CVE-2026-74624
netfilter: nf_conntrack: defer invalid log until after unlock
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.
INFO
Published Date :
Aug. 22, 2026, 4:16 p.m.
Last Modified :
Aug. 22, 2026, 4:16 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-74624
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Apply the kernel patch that defers invalid packet logging.
- Store minimal log context while lock is held.
- Emit logs after the lock is released.
- Add lockdep assertions for future checks.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-74624.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-74624 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-74624
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-74624 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-74624 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 22, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'd9a6f0d0df1899ff9086a57abc600e414f4b8cdd', 'lessThan': '63853eb20bba4e00b7cd0b8cfc19337bbaaf5037', 'versionType': 'git'}, {'status': 'affected', 'version': 'd9a6f0d0df1899ff9086a57abc600e414f4b8cdd', 'lessThan': '9480fcf70a5aa9d320088a01c95df0e5e6391f4a', 'versionType': 'git'}, {'status': 'affected', 'version': 'd9a6f0d0df1899ff9086a57abc600e414f4b8cdd', 'lessThan': '0424186d570aa4d1ad17f516afb86bd9eaa4f42e', 'versionType': 'git'}, {'status': 'affected', 'version': 'd9a6f0d0df1899ff9086a57abc600e414f4b8cdd', 'lessThan': 'c0224327b7cbed9d3198e8dbec847281053dcd06', 'versionType': 'git'}, {'status': 'affected', 'version': 'd9a6f0d0df1899ff9086a57abc600e414f4b8cdd', 'lessThan': '2d19b95c9723001f214f7a47d67b09f46238f200', 'versionType': 'git'}], 'programFiles': ['net/netfilter/nf_conntrack_proto.c', 'net/netfilter/nf_conntrack_proto_sctp.c', 'net/netfilter/nf_conntrack_proto_tcp.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.1'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.1', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.152', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.104', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.45', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.9', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/netfilter/nf_conntrack_proto.c', 'net/netfilter/nf_conntrack_proto_sctp.c', 'net/netfilter/nf_conntrack_proto_tcp.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/0424186d570aa4d1ad17f516afb86bd9eaa4f42e Added Reference https://git.kernel.org/stable/c/2d19b95c9723001f214f7a47d67b09f46238f200 Added Reference https://git.kernel.org/stable/c/63853eb20bba4e00b7cd0b8cfc19337bbaaf5037 Added Reference https://git.kernel.org/stable/c/9480fcf70a5aa9d320088a01c95df0e5e6391f4a Added Reference https://git.kernel.org/stable/c/c0224327b7cbed9d3198e8dbec847281053dcd06