CVE-2025-40149
BaseFortify
Publication date: 2025-11-12
Last updated on: 2026-02-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.2 (inc) to 6.6.121 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.66 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.161 (exc) |
| linux | linux_kernel | From 4.18 (inc) to 5.15.199 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.17.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the function get_netdev_for_sock() which is called during setsockopt() and is not under RCU (Read-Copy-Update). The issue is that using sk_dst_get(sk)->dev could trigger a Use-After-Free (UAF) condition. The fix involves using __sk_dst_get() and dst_dev_rcu() instead to avoid this unsafe access.
How can this vulnerability impact me? :
The vulnerability could lead to a Use-After-Free condition in the Linux kernel, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges by exploiting the kernel memory corruption.