Skip to content
EXYS
Back to the CVEs

CVE-2024-36971

7.8, high Known exploited

Android Kernel Remote Code Execution Vulnerability

NVD (opens in a new tab) CVE.org (opens in a new tab) CISA KEV catalogue (opens in a new tab)
CVSS
7.8, high high CVSS v3.1
EPSS, next 30 days
3% higher than 85.6% of scored CVEs
Exploitation
Confirmed in the wild
Published
10 Jun 20242 years ago

Known exploited

CISA added this to the Known Exploited Vulnerabilities Catalog on 7 Aug 2024. US federal agencies had to remediate by 28 Aug 2024, a deadline that has passed.

Required action. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

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.

Details

Vendor
Android
Product
Linux
Weakness
CWE-416 (opens in a new tab)
Status
Analyzed
Updated
17 Jun 2026
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References 10

Patches and fixes 8

Other references 2

The kind is read from NVD's tags where present and from the shape of the URL otherwise, so treat it as a hint.

Other Android CVEs

Every Android CVE we hold

Same vendor in what we hold, not a known link between the flaws.

  • CVE-2025-48595 Android Framework Integer Overflow Vulnerability KEV EPSS 2% 8.4, high
  • CVE-2025-48572 Android Framework Privilege Escalation Vulnerability KEV EPSS 0.3% 7.8, high
  • CVE-2025-48633 Android Framework Information Disclosure Vulnerability KEV EPSS 0.3% 5.5, medium
  • CVE-2025-48543 Android Runtime Use-After-Free Vulnerability KEV EPSS 0.6% 8.8, high
  • CVE-2024-43093 Android Framework Privilege Escalation Vulnerability KEV EPSS 0.7% 7.3, high
  • CVE-2024-32896 Android Pixel Privilege Escalation Vulnerability KEV EPSS 3% 7.8, high
  • CVE-2024-29745 Android Pixel Information Disclosure Vulnerability KEV EPSS 0.5% 5.5, medium
  • CVE-2024-29748 Android Pixel Privilege Escalation Vulnerability KEV EPSS 0.7% 7.8, high

Beyond this page

Is CVE-2024-36971 in your network?

This page tells you how dangerous CVE-2024-36971 is out there. Whether it sits on one of your devices, only a scan of your own network can tell. That is what our systems do, every day, for the companies we protect.

CVE-2024-36971 is in the CISA catalogue of exploited vulnerabilities: attackers are already exploiting it.

  • EXYS7600 OCELOT

    Find it before attackers do

    Ocelot scans your network on a schedule and reports every vulnerability it finds by its CVE identifier, with its CVSS score and how many of your hosts are affected. A finding like CVE-2024-36971 comes with the devices to patch.

    Learn more about EXYS7600 OCELOT

  • EXYS7950 KONDRA

    Detect it if it's exploited

    Until the patch is applied, Kondra monitors your network, events and endpoints in real time. It keeps an inventory of the software installed on every endpoint, and its anomaly detection rules flag what an attacker does once inside.

    Learn more about EXYS7950 KONDRA
Check your exposure

Assembled from the NVD 2.0 API, the CISA Known Exploited Vulnerabilities Catalog and FIRST EPSS. Scores are as of our last collection on 17 Oct 2026, not the live upstream state.