CVE-2024-41042
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| rhel | 9 | fixed | |
| rocky | 8 | fixed | |
| sles | affected | | |
| debian | bookworm | fixed | 6.1.106-1 |
| debian | bullseye | fixed | 5.10.226-1 |
| debian | forky | fixed | 6.9.10-1 |
| debian | sid | fixed | 6.9.10-1 |
| debian | trixie | fixed | 6.9.10-1 |
| almalinux | 8 | fixed | kernel-doc-4.18.0-553.27.1.el8_10.noarch.rpm |
References
- https://access.redhat.com/errata/RHSA-2024:9315
- https://errata.rockylinux.org/RLSA-2024:8870
- https://errata.rockylinux.org/RLSA-2024:8856
- https://www.suse.com/security/cve/CVE-2024-41042.html
- https://security-tracker.debian.org/tracker/CVE-2024-41042
- https://access.redhat.com/errata/RHSA-2024:8856
- https://bugzilla.redhat.com/2266247
- https://bugzilla.redhat.com/2269183
- https://bugzilla.redhat.com/2275750
- https://bugzilla.redhat.com/2277168
- https://bugzilla.redhat.com/2278262
- https://bugzilla.redhat.com/2278350
- https://bugzilla.redhat.com/2278387
- https://bugzilla.redhat.com/2281284
- https://bugzilla.redhat.com/2281669
- https://bugzilla.redhat.com/2281817
- https://bugzilla.redhat.com/2293356
- https://bugzilla.redhat.com/2293402
- https://bugzilla.redhat.com/2293458
- https://bugzilla.redhat.com/2293459
- https://bugzilla.redhat.com/2297475
- https://bugzilla.redhat.com/2297508
- https://bugzilla.redhat.com/2297545
- https://bugzilla.redhat.com/2297567
- https://bugzilla.redhat.com/2297568
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.