# CVE-2024-36971: Android Kernel Remote Code Execution > A race condition in the Linux kernel network stack allows attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 7 Aug 2024 (CISA KEV) - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jun 2024 - **Updated:** 5 Aug 2026 - **Also known as:** A-343727534, ASB-A-343727534, AZL-42615, AZL-42622, BELL-CVE-2024-36971, DEBIAN-CVE-2024-36971, GHSA-3rf3-8wmx-cm8q, RHSA-2024:5388, RHSA-2024:5519, RHSA-2024:5521, RHSA-2024:5523, SUSE-SU-2025:0242-1, SUSE-SU-2025:0250-1, UBUNTU-CVE-2024-36971 ## What is CVE-2024-36971? CVE-2024-36971 is a high-severity use after free vulnerability in Debian Debian Linux, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2024-36971? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kpatch-patch-5_14_0-427_13_1` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-2.el9_4 | | `kpatch-patch-5_14_0-427_13_1-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-2.el9_4 | | `kpatch-patch-5_14_0-427_13_1-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-2.el9_4 | | `bpftool` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `bpftool-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-abi-whitelists` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-core` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debug` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debug-core` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debug-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debug-devel` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debug-modules` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debug-modules-extra` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-devel` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-doc` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-modules` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-modules-extra` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-tools` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-tools-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kernel-tools-libs` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `perf` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `perf-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `python3-perf` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `python3-perf-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:4.18.0-193.138.1.el8_2 | | `kpatch-patch-4_18_0-305_120_1` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:1-4.el8_4 | | `kpatch-patch-4_18_0-305_120_1-debuginfo` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:1-4.el8_4 | | `kpatch-patch-4_18_0-305_120_1-debugsource` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:1-4.el8_4 | | `kpatch-patch-5_14_0-284_48_1` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1-5.el9_2 | | `kpatch-patch-5_14_0-284_48_1-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1-5.el9_2 | | `kpatch-patch-5_14_0-284_48_1-debugsource` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1-5.el9_2 | | `kpatch-patch-5_14_0-284_52_1` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1-4.el9_2 | | `kpatch-patch-5_14_0-284_52_1-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1-4.el9_2 | | `kpatch-patch-5_14_0-284_52_1-debugsource` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1-4.el9_2 | | `kernel-livepatch-SLE15-SP3_Update_40` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 16-150300.2.1 | | `kernel-livepatch-SLE15-SP3_Update_41` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 15-150300.2.1 | | `kernel-livepatch-SLE15-SP4_Update_22` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 14-150400.2.1 | Products: Debian Debian Linux, Linux kernel. ## How do I fix CVE-2024-36971? Apply the vendor's patch. US federal agencies must fix it by 28 Aug 2024. ## Is CVE-2024-36971 being exploited? Yes. Attackers have exploited CVE-2024-36971 in the wild since at least 7 Aug 2024. Public exploit code: - Poc for CVE-2024-36971 (github_poc): https://github.com/M4G1XX/CVE-2024-36971 ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-36971 and fix it if it is affected. What it is: CVE-2024-36971 is a high-severity use after free vulnerability in Debian Debian Linux, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2024-36971 in the wild since at least 7 Aug 2024. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-36971/ (Markdown: https://insights.sbomify.com/CVE-2024-36971/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36971 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36971 - OSV: https://osv.dev/vulnerability/CVE-2024-36971 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-36971/ Summaries are generated and may contain mistakes; the official description above is the record.