CVE-2026-23002
BaseFortify
Publication date: 2026-01-25
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.12 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.7 (exc) |
| 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 6.12.1 (inc) to 6.12.67 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves improper handling of file reading in a sleepable context. Specifically, the code was using direct page cache access via read_cache_folio(), which could lead to a kernel NULL pointer dereference bug in filemap_read_folio. The fix changes the code to use __kernel_read() for sleepable contexts, which is a safer, standard kernel file reading interface that handles the complexity of reading file data and prevents the crash.
How can this vulnerability impact me? :
This vulnerability could cause the Linux kernel to crash due to a NULL pointer dereference when reading files in certain contexts. Such a crash can lead to system instability or denial of service, affecting the reliability and availability of the system.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch that updates the Linux kernel to use __kernel_read() for sleepable contexts in lib/buildid, which prevents the kernel NULL pointer dereference in filemap_read_folio. This involves updating your kernel to a version that includes this fix.