Answer in brief
CVE-2026-74490 records a Unknown severity vulnerability in tipc: avoid use-after-free in poll trace queue dumps. 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 | >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <d7940bb6a8e7ab28f972c2875cb05783216312dc || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <bed792737b5f1ba773054dbe984502958bdfe6ce || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <ac2f787980fdf4364cd5651a4c8128e59b8de3aa || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <b4f1719dfea023220e0e6bd892b087d76b2a6a49 | d7940bb6a8e7ab28f972c2875cb05783216312dc, 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d, bed792737b5f1ba773054dbe984502958bdfe6ce, ac2f787980fdf4364cd5651a4c8128e59b8de3aa, b4f1719dfea023220e0e6bd892b087d76b2a6a49 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: tipc: avoid use-after-free in poll trace queue dumps TIPC socket tracepoints dump queue state through tipc_sk_dump(). Most queue-dump callsites already serialize that walk under the socket lock or sk->sk_lock.slock, but tipc_poll() calls trace_tipc_sk_poll(..., TIPC_DUMP_ALL, ...) without holding either lock. That lets the poll trace path reach tipc_list_dump() and backlog head/tail dumping while another context dequeues and frees an skb, leaving the trace helper dereferencing a stale queue entry. Stop the unlocked poll trace site from requesting queue dumps. Other queue dump trace callsites keep their existing output under the locking they already provide, while poll still emits the event itself without walking live queue members from an unlocked context.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74490 records a Unknown severity vulnerability in tipc: avoid use-after-free in poll trace queue dumps. 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 | >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <d7940bb6a8e7ab28f972c2875cb05783216312dc || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <bed792737b5f1ba773054dbe984502958bdfe6ce || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <ac2f787980fdf4364cd5651a4c8128e59b8de3aa || >=b4b9771bcbbd5839b0f77aba55e2f85989ed6779 <b4f1719dfea023220e0e6bd892b087d76b2a6a49 | d7940bb6a8e7ab28f972c2875cb05783216312dc, 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d, bed792737b5f1ba773054dbe984502958bdfe6ce, ac2f787980fdf4364cd5651a4c8128e59b8de3aa, b4f1719dfea023220e0e6bd892b087d76b2a6a49 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: tipc: avoid use-after-free in poll trace queue dumps TIPC socket tracepoints dump queue state through tipc_sk_dump(). Most queue-dump callsites already serialize that walk under the socket lock or sk->sk_lock.slock, but tipc_poll() calls trace_tipc_sk_poll(..., TIPC_DUMP_ALL, ...) without holding either lock. That lets the poll trace path reach tipc_list_dump() and backlog head/tail dumping while another context dequeues and frees an skb, leaving the trace helper dereferencing a stale queue entry. Stop the unlocked poll trace site from requesting queue dumps. Other queue dump trace callsites keep their existing output under the locking they already provide, while poll still emits the event itself without walking live queue members from an unlocked context.
Quoted source text, attributed separately from HOL analysis.