Strix
57.4K

CVE-2026-74624

Unknown

Last modified

CVE-2026-74624 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: defer invalid log until after unlock TCP and SCTP conntrack paths can emit invalid-packet logs while ct->lock is still held. When invalid logging is routed to nfnetlink_log and conntrack export is enabled, the log path can re-enter conntrack netlink glue and dump the same conntrack again. Protocol attribute dumping may take ct->lock, so logging while holding that lock can deadlock. Defer the TCP invalid logs by storing only the minimal log context while ct->lock is held and emitting the log after unlocking.

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: defer invalid log until after unlock TCP and SCTP conntrack paths can emit invalid-packet logs while ct->lock is still held. When invalid logging is routed to nfnetlink_log and conntrack export is enabled, the log path can re-enter conntrack netlink glue and dump the same conntrack again. Protocol attribute dumping may take ct->lock, so logging while holding that lock can deadlock. Defer the TCP invalid logs by storing only the minimal log context while ct->lock is held and emitting the log after unlocking. Also make the TCP timeout-lowering invalid path return whether a log is needed, then emit that log after unlocking. Do the same for the SCTP invalid state-transition log that can be reached while ct->lock is held. Add a lockdep assertion to nf_ct_l4proto_log_invalid() so future callers that log invalid conntracks while holding ct->lock are caught outside TCP and SCTP as well.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < ca97360eba4b3dc67f1804625542f4ccc774242a; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 63853eb20bba4e00b7cd0b8cfc19337bbaaf5037; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 9480fcf70a5aa9d320088a01c95df0e5e6391f4a; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 0424186d570aa4d1ad17f516afb86bd9eaa4f42e; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < c0224327b7cbed9d3198e8dbec847281053dcd06; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 2d19b95c9723001f214f7a47d67b09f46238f200
LinuxLinux6.1

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74624?
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: defer invalid log until after unlock TCP and SCTP conntrack paths can emit invalid-packet logs while ct->lock is still held. When invalid logging is routed to nfnetlink_log and conntrack export is enabled, the log path can re-enter conntrack netlink glue and dump the same conntrack again. Protocol attribute dumping may take ct->lock, so logging while holding that lock can deadlock. Defer the TCP invalid logs by storing only the minimal log context while ct->lock is held and emitting the log after unlocking. Also make the TCP timeout-lowering invalid path return whether a log is needed, then emit that log after unlocking. Do the same for the SCTP invalid state-transition log that can be reached while ct->lock is held. Add a lockdep assertion to nf_ct_l4proto_log_invalid() so future callers that log invalid conntracks while holding ct->lock are caught outside TCP and SCTP as well.
How severe is CVE-2026-74624?
Severity scoring for CVE-2026-74624 is pending analysis.
How do I fix CVE-2026-74624?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-74624?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST