Linux Kernel: __dst_negative_advice Race Enables UAF via RCU Violation
CVE-2024-36971 Published on June 10, 2024

net: fix __dst_negative_advice() race
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.

NVD

Known Exploited Vulnerability

This Android Kernel Remote Code Execution Vulnerability is part of CISA's list of Known Exploited Vulnerabilities. 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.

The following remediation steps are recommended / required by August 28, 2024: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Vulnerability Analysis

CVE-2024-36971 can be exploited with local system access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. This vulnerability is known to be actively exploited by threat actors. The potential impact of an exploit of this vulnerability is considered to be very high.

Attack Vector:
LOCAL
Attack Complexity:
LOW
Privileges Required:
LOW
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
HIGH
Availability Impact:
HIGH

Weakness Type

What is a Dangling pointer Vulnerability?

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

CVE-2024-36971 has been classified to as a Dangling pointer vulnerability or weakness.


Products Associated with CVE-2024-36971

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2024-36971 are published in these products:

 
 
 
 

Affected Versions

Linux: Linux: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel: linux_kernel:

Exploit Probability

EPSS
0.49%
Percentile
65.57%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.