CVE-2026-23007
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.11 |
| 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.11.1 (inc) to 6.18.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-908 | The product uses or accesses a resource that has not been initialized. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the auto-generated integrity buffer used for writes to block devices. The buffer is not fully initialized before being passed to the underlying device, which means uninitialized memory can be exposed and read by userspace or anyone with physical access to the storage device. Specifically, when protection information (PI) is generated and the PI tuple size is nonzero but the metadata size is larger than the PI tuple, the extra portion of the metadata remains uninitialized, potentially leaking sensitive data.
How can this vulnerability impact me? :
This vulnerability can lead to unintended exposure of uninitialized memory contents from the storage device to userspace or anyone with physical access. This could result in leakage of sensitive or confidential data stored in memory, potentially compromising system security and privacy.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the issue has been resolved. Ensure that the auto-generated integrity buffer for writes is fully initialized before being passed to the underlying block device, as per the fix described. There are no specific configuration changes or commands provided to mitigate this vulnerability other than applying the kernel patch or update.