CVE-2024-36971
HighExploitedPublic exploitLinux kernel: net: fix dst_negative_advice() race
Published Jun 10, 2024 · Updated Oct 14, 2026 · Also known as A-343727534, ASB-A-343727534, DEBIAN-CVE-2024-36971, UBUNTU-CVE-2024-36971
Key Facts
Patch immediately- CVE-2024-36971 is a high-severity vulnerability (CVSS 7.8 v3.1) affecting Debian Linux, Linux Kernel, Linux (debian) and 22 more products.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Aug 5, 2024. Public exploit code is available.
- EPSS estimates a 2.7% probability of exploitation in the next 30 days.
- Fixed versions are available, including :linux_kernel: :2024-08-05, bpftool 3.10.0-1160.119.1.0.3.el7, bpftool 4.18.0-553.16.1.el8_10.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
2.7%
Higher than 85.6% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2024-36971 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
In 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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Aug 7, 2024 | Aug 28, 2024 | Not reported |
| Industry KEV feed | Aug 5, 2024 | Aug 28, 2024 | Not reported |
| CIRCL KEV | Aug 7, 2024 | Aug 28, 2024 | Not reported |
| ENISA EUVD | Aug 7, 2024 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected Products
1,056 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Debian LinuxDebian | 10.0 | n/a |
| Linux KernelLinux | See advisory | 4.19.316 |
| Linuxdebian | >= a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 | 5.10.221-1 |
| rootio-linuxrootio | See advisory | 5.10.221-1 |
| linux-allwinner-5.19ubuntu | See advisory | n/a |
Patched Releases
:linux_kernel:
:2024-08-05
bpftool
3.10.0-1160.119.1.0.3.el7, 4.18.0-553.16.1.el8_10, 5.10.219-1.ph4, 6.1.177-1.ph5, 6.1.94-1.ph5, 6.1.94-99.176.amzn2023, 7.3.0-427.31.1.el9_4
cluster-md-kmp-64kb
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
cluster-md-kmp-azure
5.14.21-150500.33.60.1, 6.4.0-150600.8.8.2
cluster-md-kmp-default
5.14.21-150400.24.125.1, 5.14.21-150500.55.73.1, 5.3.18-150200.24.206.1, 5.3.18-150300.59.179.1, 6.4.0-150600.23.14.2
cluster-md-kmp-rt
5.14.21-150500.13.61.1, 6.4.0-150600.10.5.1
dlm-kmp-64kb
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dlm-kmp-azure
5.14.21-150500.33.60.1, 6.4.0-150600.8.8.2
dlm-kmp-default
5.14.21-150400.24.125.1, 5.14.21-150500.55.73.1, 5.3.18-150200.24.206.1, 5.3.18-150300.59.179.1, 6.4.0-150600.23.14.2
dlm-kmp-rt
5.14.21-150500.13.61.1, 6.4.0-150600.10.5.1
dtb-aarch64
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-allwinner
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-altera
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-amazon
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-amd
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-amlogic
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-apm
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-apple
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-arm
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-broadcom
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-cavium
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-exynos
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-freescale
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-hisilicon
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
dtb-lg
5.14.21-150500.55.73.1, 6.4.0-150600.23.14.1
Timeline
Publicly disclosed
Jun 10, 2024
Added to Industry KEV feed
Aug 5, 2024
Added to CISA KEV
Aug 7, 2024
Added to CIRCL KEV
Aug 7, 2024
Added to ENISA EUVD
Aug 7, 2024
Last updated
Oct 14, 2026
Weakness Type
- CWE-416 Use After Free
References
- advisoryRHSA-2024:5101
- advisoryRHSA-2024:5102
- advisoryRHSA-2024:5200
- advisoryRHSA-2024:5255
- advisoryRHSA-2024:5256
FAQ
Common Questions.
In 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.
Affected: Debian Linux versions 10.0; Linux Kernel; Linux (debian) versions >= a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Aug 5, 2024.
Yes. It was added on Aug 7, 2024 with a federal remediation due date of Aug 28, 2024.
Public exploit code is available.
Fixed versions are available, including :linux_kernel: :2024-08-05, bpftool 3.10.0-1160.119.1.0.3.el7, bpftool 4.18.0-553.16.1.el8_10.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2024-36971 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo