CVE-2024-26925: netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path
The commit mutex should not be released during the critical section
between nft_gc_seq_begin() and nft_gc_seq_end(), otherwise, async GC
worker could collect expired objects and get the released commit lock
within the same GC sequence.
nf_tables_module_autoload() temporarily releases the mutex to load
module dependencies, then it goes back to replay the transaction again.
Move it at the end of the abort phase after nft_gc_seq_end() is called.
Security readout for executives and security teams
Plain-English summary
CVE-2024-26925 is a Linux kernel nf_tables locking flaw. Under specific transaction-abort and garbage-collection timing, kernel cleanup can run while a commit lock has been released too early. The bundle does not provide CVSS, impact class, or confirmed exploitation, so urgency depends on Linux exposure and vendor kernel status.
Executive priority
Treat as a kernel maintenance priority with uncertain severity. Patch through normal security update channels, escalating for shared Linux infrastructure, security appliances, or environments where kernel compromise would have broad operational impact.
Technical view
The issue is in Linux netfilter nf_tables. The commit mutex could be released inside the critical section between nft_gc_seq_begin() and nft_gc_seq_end(), letting an async GC worker collect expired objects and acquire the released commit lock in the same GC sequence. Stable fixes move module autoload mutex release after nft_gc_seq_end() during abort handling.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions with nf_tables/netfilter available. The bundle lists multiple affected stable-series versions, including 5.4.274, 5.10.215, 5.15.155, 6.1.86, 6.6.26, 6.8.5, and 6.9.
Exploitation context
The provided sources do not state active exploitation, and KEV is false. The description suggests a race in kernel transaction cleanup, but the bundle does not provide exploit prerequisites, attacker position, or impact details.
Researcher notes
Evidence is incomplete for impact and exploitation. Analysis should focus on affected kernel lineage, nf_tables transaction abort behavior, and whether vendor backports include the mutex-ordering fix. Avoid assuming exploitability beyond the provided race description.
Mitigation direction
Upgrade to a vendor kernel that includes the referenced stable Linux fixes.
Check Debian, Siemens, or relevant vendor advisories for product-specific remediation.
Prioritize systems using nftables/netfilter in shared or exposed environments.
Track distribution kernel package status rather than applying raw commits blindly.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and container hosts.
Check whether deployed kernels are listed as affected in vendor advisories.
Confirm updated kernels include the referenced stable fix commits.
Verify nftables/netfilter exposure where local policy permits.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26925 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.