CVE-2026-74624: Linux Vulnerability (CVSS 7.5)

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.

Metrics

CVSS 3.1

7.5/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS Probability

0.48%

39.9th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

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

Vendor	Product	Versions
Linux	Linux	>= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < ca97360eba4b3dc67f1804625542f4ccc774242a; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 63853eb20bba4e00b7cd0b8cfc19337bbaaf5037; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 9480fcf70a5aa9d320088a01c95df0e5e6391f4a; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 0424186d570aa4d1ad17f516afb86bd9eaa4f42e; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < c0224327b7cbed9d3198e8dbec847281053dcd06; >= d9a6f0d0df1899ff9086a57abc600e414f4b8cdd, < 2d19b95c9723001f214f7a47d67b09f46238f200
Linux	Linux	6.1

References

Timeline

Published: Aug 22, 2026
Last Modified: Oct 16, 2026
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?

CVE-2026-74624 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 0.48% probability of exploitation in the next 30 days.

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 →