---
id: "CVE-2024-36971"
kind: "vulnerability"
aliases: ["CVE-2024-36971"]
title: "In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race\u2026"
severity: "critical"
cvss: 7.8
epss: null
exploited: true
status: "open"
category: "infrastructure"
products: [{"name": "Android Kernel", "fixed": [], "affected": "", "ecosystem": "vendor"}, {"name": "debian linux", "fixed": [], "affected": "= 10.0", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["4.19.316"], "affected": ">= 4.6, < 4.19.316", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["5.4.278"], "affected": ">= 4.20, < 5.4.278", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["5.10.219"], "affected": ">= 5.5, < 5.10.219", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["5.15.161"], "affected": ">= 5.11, < 5.15.161", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.1.94"], "affected": ">= 5.16, < 6.1.94", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.6.34"], "affected": ">= 6.2, < 6.6.34", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.9.4"], "affected": ">= 6.7, < 6.9.4", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["android", "exploited", "infrastructure", "linux-kernel"]
not_affected_if: ["unknown"]
published_at: "2024-06-10T09:15:09+00:00"
first_seen_at: "2026-10-23T19:11:51+00:00"
updated_at: "2026-10-23T22:29:05+00:00"
sources: [{"source": "kev", "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2024-36971", "first_seen_at": "2026-10-23T19:11:51+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36971", "first_seen_at": "2026-10-23T22:29:05+00:00"}]
---

# In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race…

An unspecified flaw in the Android kernel (Linux kernel code) allows remote code execution. CISA lists it as actively exploited in the wild.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:Android Kernel affected ? fixed ?
- vendor:debian linux affected = 10.0 fixed ?
- vendor:linux kernel affected >= 4.6, < 4.19.316 fixed 4.19.316
- vendor:linux kernel affected >= 4.20, < 5.4.278 fixed 5.4.278
- vendor:linux kernel affected >= 5.5, < 5.10.219 fixed 5.10.219
- vendor:linux kernel affected >= 5.11, < 5.15.161 fixed 5.15.161
- vendor:linux kernel affected >= 5.16, < 6.1.94 fixed 6.1.94
- vendor:linux kernel affected >= 6.2, < 6.6.34 fixed 6.6.34
- vendor:linux kernel affected >= 6.7, < 6.9.4 fixed 6.9.4

## Fix

Apply the mitigations per vendor instructions (Android security bulletin); if unavailable, discontinue use of the affected product per CISA's required action.

## Timeline

- 2026-10-23T19:11:51+00:00 kev https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2024-36971
- 2026-10-23T22:29:05+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2024-36971

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_