Answer in brief
CVE-2024-36971 records a High severity (CVSS 7.8) vulnerability in net: fix __dst_negative_advice() race. The current sources mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. Known-exploitation status makes exposure review time-sensitive. 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), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <051c0bde9f0450a2ec3d62a86d2a0d2fad117f13 || >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <db0082825037794c5dba9959c9de13ca34cc5e72 || >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <2295a7ef5c8c49241bff769e7826ef2582e532a6 || >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <eacb8b195579c174a6d3e12a9690b206eb7f28cf || >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <81dd3c82a456b0015461754be7cb2693991421b4 || >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <5af198c387128a9d2ddd620b0f0803564a4d4508 || >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <b8af8e6118a6605f0e495a58d591ca94a85a50fc || >=a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 <92f1655aa2b2294d0b49925f3b875a634bd3b59e | 051c0bde9f0450a2ec3d62a86d2a0d2fad117f13, db0082825037794c5dba9959c9de13ca34cc5e72, 2295a7ef5c8c49241bff769e7826ef2582e532a6, eacb8b195579c174a6d3e12a9690b206eb7f28cf, 81dd3c82a456b0015461754be7cb2693991421b4, 5af198c387128a9d2ddd620b0f0803564a4d4508, b8af8e6118a6605f0e495a58d591ca94a85a50fc, 92f1655aa2b2294d0b49925f3b875a634bd3b59e |
| Linux/Linuxgeneric | 4.6 | Not reported |
| linux/linux_kernelgeneric | 4.6 | Not reported |
| linux/linux_kernelgeneric | >=a87cb3e48ee8 <051c0bde9f04 || >=a87cb3e48ee8 <db0082825037 || >=a87cb3e48ee8 <2295a7ef5c8c || >=a87cb3e48ee8 <eacb8b195579 || >=a87cb3e48ee8 <81dd3c82a456 || >=a87cb3e48ee8 <5af198c38712 || >=a87cb3e48ee8 <b8af8e6118a6 || >=a87cb3e48ee8 <92f1655aa2b2 | 051c0bde9f04, db0082825037, 2295a7ef5c8c, eacb8b195579, 81dd3c82a456, 5af198c38712, b8af8e6118a6, 92f1655aa2b2 |
| linux/linux_kernelgeneric | * | Not reported |
Published upstream
Jun 10, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Aug 7, 2024
Evidence: source:kev:kev:kev:recordIn the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.
Quoted source text, attributed separately from HOL analysis.