Answer in brief
CVE-2026-74624 records a Unknown severity vulnerability in netfilter: nf_conntrack: defer invalid log until after unlock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d9a6f0d0df1899ff9086a57abc600e414f4b8cdd <63853eb20bba4e00b7cd0b8cfc19337bbaaf5037 || >=d9a6f0d0df1899ff9086a57abc600e414f4b8cdd <9480fcf70a5aa9d320088a01c95df0e5e6391f4a || >=d9a6f0d0df1899ff9086a57abc600e414f4b8cdd <0424186d570aa4d1ad17f516afb86bd9eaa4f42e || >=d9a6f0d0df1899ff9086a57abc600e414f4b8cdd <c0224327b7cbed9d3198e8dbec847281053dcd06 || >=d9a6f0d0df1899ff9086a57abc600e414f4b8cdd <2d19b95c9723001f214f7a47d67b09f46238f200 | 63853eb20bba4e00b7cd0b8cfc19337bbaaf5037, 9480fcf70a5aa9d320088a01c95df0e5e6391f4a, 0424186d570aa4d1ad17f516afb86bd9eaa4f42e, c0224327b7cbed9d3198e8dbec847281053dcd06, 2d19b95c9723001f214f7a47d67b09f46238f200 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
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.
Quoted source text, attributed separately from HOL analysis.