Repository navigation
[ciqlts8_6] netfilter: nf_tables: do not allow RULE_ID to refer to another chain - #1724
Conversation
|
🤖 Validation Checks In Progress Workflow run: https://github.com/ctrliq/kernel-src-tree/actions/runs/39681983376 |
🔍 Upstream Linux Kernel Commit Check
This is an automated message from the kernel commit checker workflow. |
❌ Diffofdiffs: 1 backport couldn't be compared with upstreamWarning 1 backport couldn't be compared. Details are in the workflow run log. 1. Backport: Show errorChecked PR revision |
|
✅ Validation checks completed successfully View full results: https://github.com/ctrliq/kernel-src-tree/actions/runs/39681983376 |
jira VULN-3159 cve CVE-2022-2586 commit-author Thadeu Lima de Souza Cascardo <cascardo@canonical.com> commit 36d5b29 When doing lookups for rules on the same batch by using its ID, a rule from a different chain can be used. If a rule is added to a chain but tries to be positioned next to a rule from a different chain, it will be linked to chain2, but the use counter on chain1 would be the one to be incremented. When looking for rules by ID, use the chain that was used for the lookup by name. The chain used in the context copied to the transaction needs to match that same chain. That way, struct nft_rule does not need to get enlarged with another member. Fixes: 1a94e38 ("netfilter: nf_tables: add NFTA_RULE_ID attribute") Fixes: 75dd48e ("netfilter: nf_tables: Support RULE_ID reference in new rule") Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com> Cc: <stable@vger.kernel.org> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org> (cherry picked from commit 36d5b29) Signed-off-by: Jonathan Maple <jmaple@ciq.com> (cherry picked from commit 67ea6fc) Signed-off-by: Jonathan Maple <jmaple@ciq.com>
ad4df08 to
42712f0
Compare
|
🤖 Validation Checks In Progress Workflow run: https://github.com/ctrliq/kernel-src-tree/actions/runs/39688913621 |
🔍 Diffofdiffs: 1 backport differs from upstreamOpen to anyone signed in to GitHub. Report expires 2027-01-19 22:37 UTC.
Checked PR revision |
🔍 Upstream Linux Kernel Commit Check
This is an automated message from the kernel commit checker workflow. |
|
✅ Validation checks completed successfully View full results: https://github.com/ctrliq/kernel-src-tree/actions/runs/39688913621 |
@PlaidCat mentioned to me on slack that although this commit isn't officially associated with the CVE, it should be |
Specifically this CVE existed before the KERNEL CNA, we always have this problem as pre-KernelCNA there isn't always a great 1:1 mapping of SHA to CVEID |
Summary
This PR has been automatically created after successful completion of all CI stages.
Commit Message(s)
Test Results
✅ Build Stage
✅ Boot Verification
✅ Kernel Selftests
✅ LTP Results
x86_64 newly passing:
🤖 This PR was automatically generated by GitHub Actions
Run ID: 39687904247