CVE-2026-23004
BaseFortify
Publication date: 2026-01-25
Last updated on: 2026-04-27
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 3.6 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 3.6.1 (inc) to 6.6.130 (exc) |
| linux | linux_kernel | From 6.12 (inc) to 6.12.78 (exc) |
| linux | linux_kernel | From 6.18 (inc) to 6.18.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's IPv6 routing code, specifically in the functions rt6_uncached_list_del() and rt_del_uncached_list(). The issue arises because the code does not properly lock a shared list before modifying it, leading to a use-after-free condition when one CPU writes to a list element that has already been freed by another CPU. This causes kernel crashes due to invalid memory access during list operations.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash unexpectedly due to a use-after-free bug triggered by race conditions in IPv6 routing list management. Such crashes can lead to system instability, denial of service, and potential disruption of network services on affected systems.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by ensuring proper locking in the functions rt6_uncached_list_del() and related IPv4 functions to prevent race conditions. Immediate mitigation involves updating the Linux kernel to a version where these fixes are applied, which includes using list_del_init_careful() and list_empty_careful(), or ensuring that rt6_uncached_list_del() always grabs the spinlock whenever rt->dst.rt_uncached_list has been set.