CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2024-36971 remediation guide

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

Open CVE record
ProductAndroid Kernel
Affected versionsa87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, 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 versions4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.94, 6.6.34, 6.9.4
Priority basisImmediate · CVSS 7.8 · EPSS 2.70%
01

Identify the affected asset

Confirm whether Android Kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 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. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

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

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2024-36971 Remediation Guide | SECUFOCUS NOW