CISA KEV · Known exploitedHigh

CVE-2024-36971

Android Kernel

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_res...

CVSS
7.8
EPSS
2.70%
84.5% percentile
CISA KEV
Listed
Published
2024.06.10
PRIORITY ASSESSMENT

Immediate review

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog.

Known exploitationConfirmed by CISA KEV
Exploit probability2.70%
Technical severityCVSS 7.8

Vulnerability overview

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_res...

Affected product and versions

Product
Android Kernel
Affected versions
a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, 4.6, a87cb3e48ee8, 10.0, >= 4.6 < 4.19.316, >= 4.20 < 5.4.278, >= 5.5 < 5.10.219, >= 5.11 < 5.15.161, >= 5.16 < 6.1.94, >= 6.2 < 6.6.34, >= 6.7 < 6.9.4
Fixed versions
4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.94, 6.6.34, 6.9.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
CISA required action

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

Due date: 2024.08.28
  1. 1
    Identify

    Confirm that Android Kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416
KEV added
2024.08.07
Ransomware use
미확인