+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2024-36971 Android Kernel Remote Code Execution Vulnerability

Android contains an unspecified vulnerability in the kernel that allows for remote code execution. This vulnerability resides in Linux Kernel and could impact other products, including but not limited to Android OS.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 7 Aug 2024.
  • Rated High severity (CVSS 7.8, scored by Vendor).
  • It has been in the catalogue for 821 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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.

Affected Versions

ProductVersions
Linux Linuxa87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to before 051c0bde9f0450a2ec3d62a86d2a0d2fad117f13
a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to before db0082825037794c5dba9959c9de13ca34cc5e72
a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to before 2295a7ef5c8c49241bff769e7826ef2582e532a6
a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to before eacb8b195579c174a6d3e12a9690b206eb7f28cf
a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to before 81dd3c82a456b0015461754be7cb2693991421b4
a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to before 5af198c387128a9d2ddd620b0f0803564a4d4508
Linux Linux4.6

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Android Kernel. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

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

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated high, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 28 Aug 2024 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Android Flaws

Get alerts for AndroidWe email you when a new Android vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2025-48595Android Framework Integer Overflow VulnerabilityAdded 2 Jun 2026CVE-2025-48633Android Framework Information Disclosure VulnerabilityAdded 2 Dec 2025CVE-2025-48572Android Framework Privilege Escalation VulnerabilityAdded 2 Dec 2025CVE-2025-48543Android Runtime Use-After-Free VulnerabilityAdded 4 Sep 2025CVE-2024-43093Android Framework Privilege Escalation VulnerabilityAdded 7 Nov 2024CVE-2024-32896Android Pixel Privilege Escalation VulnerabilityAdded 13 Jun 2024

All 17 exploited Android vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2024-36971 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2024-36971
  3. CVE record: CVE-2024-36971
  4. FIRST EPSS
  5. git.kernel.org/stable/c/051c0bde9f0450a2ec3d62a86d2a0d2fad117f13
  6. git.kernel.org/stable/c/db0082825037794c5dba9959c9de13ca34cc5e72
  7. git.kernel.org/stable/c/2295a7ef5c8c49241bff769e7826ef2582e532a6
  8. git.kernel.org/stable/c/eacb8b195579c174a6d3e12a9690b206eb7f28cf
  9. git.kernel.org/stable/c/81dd3c82a456b0015461754be7cb2693991421b4
  10. git.kernel.org/stable/c/5af198c387128a9d2ddd620b0f0803564a4d4508
  11. git.kernel.org/stable/c/b8af8e6118a6605f0e495a58d591ca94a85a50fc
  12. git.kernel.org/stable/c/92f1655aa2b2294d0b49925f3b875a634bd3b59e