Skip to main content

Known exploited vulnerability · CISA KEV

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.

CVE-2024-36971

Exploited in the wild. Fix this first.

CISA added it to the Known Exploited Vulnerabilities catalog on 2024-08-07: attackers are using it right now.

CISA KEV
Listed
Added 2024-08-07 · federal fix-by 2024-08-28
EPSS (30 days)
2.7%
Higher than 86% of CVEs · 2026-11-01
CVSS v3.1
7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What CISA says

Android Kernel Remote Code Execution Vulnerability

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

NVD description · published 2024-06-10

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.

Full record on NVD

Got a whole scan? Scan Hub runs this check on every finding in your Nessus, Qualys, Rapid7 or OpenVAS export and ranks the report by it.

Try it free

How to check if you are exposed to CVE-2024-36971

  1. Find every Android Kernel system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
  2. Compare each version with the fixed versions in the vendor advisory below. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
  3. Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2024-36971.

US federal agencies had to fix this by 2024-08-28. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.

Affected versions

Versions the National Vulnerability Database lists as vulnerable to CVE-2024-36971. Check the vendor advisory for the exact fixed builds before you sign anything off.

ProductVulnerable versions
Linux Kernelfrom 4.6 before 4.19.316; from 4.20 before 5.4.278; from 5.5 before 5.10.219; from 5.11 before 5.15.161; from 5.16 before 6.1.94; from 6.2 before 6.6.34 and 1 more
Debian Linux10.0

Timeline

  1. · Published in the National Vulnerability Database
  2. · Added to CISA's Known Exploited Vulnerabilities catalog, 58 days after it was published
  3. · Fix-by date for US federal agencies, passed 795 days ago

Vendor advisories and fixes

Weakness type

More exploited Android vulnerabilities

CISA lists 17 exploited Android vulnerabilities. The closest matches:

Keep going

Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.

Cookie preferences

Essential site functions remain available whichever option you choose. Your advertising choice is saved on this site. The Scan Hub has a separate choice.

Google and Reddit may receive cookies, identifiers, browser and device information, and your network/IP information. Reject or withdraw at any time. Read the Privacy Policy.