netfilter: nf_conntrack: defer invalid log until after unlock
Summary
| CVE | CVE-2026-74624 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-08-22 16:16:35 UTC |
|---|
| Updated | 2026-08-23 13:16:47 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected d9a6f0d0df1899ff9086a57abc600e414f4b8cdd ca97360eba4b3dc67f1804625542f4ccc774242a git |
Not specified |
| CNA |
Linux |
Linux |
affected d9a6f0d0df1899ff9086a57abc600e414f4b8cdd 63853eb20bba4e00b7cd0b8cfc19337bbaaf5037 git |
Not specified |
| CNA |
Linux |
Linux |
affected d9a6f0d0df1899ff9086a57abc600e414f4b8cdd 9480fcf70a5aa9d320088a01c95df0e5e6391f4a git |
Not specified |
| CNA |
Linux |
Linux |
affected d9a6f0d0df1899ff9086a57abc600e414f4b8cdd 0424186d570aa4d1ad17f516afb86bd9eaa4f42e git |
Not specified |
| CNA |
Linux |
Linux |
affected d9a6f0d0df1899ff9086a57abc600e414f4b8cdd c0224327b7cbed9d3198e8dbec847281053dcd06 git |
Not specified |
| CNA |
Linux |
Linux |
affected d9a6f0d0df1899ff9086a57abc600e414f4b8cdd 2d19b95c9723001f214f7a47d67b09f46238f200 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.1 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.184 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.152 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.104 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.45 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.9 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/2d19b95c9723001f214f7a47d67b09f46238f200 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9480fcf70a5aa9d320088a01c95df0e5e6391f4a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0424186d570aa4d1ad17f516afb86bd9eaa4f42e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ca97360eba4b3dc67f1804625542f4ccc774242a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c0224327b7cbed9d3198e8dbec847281053dcd06 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/63853eb20bba4e00b7cd0b8cfc19337bbaaf5037 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.