CVE-2025-38073
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-12-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 block device handling. When the block size is changed concurrently with read operations, specifically between set_blocksize and read paths, it can cause a conflict. For example, if a process reads data with a smaller block size and another process changes the block size to a larger value simultaneously, the kernel may attempt to submit a read operation with a NULL block device pointer, leading to a kernel crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a race condition when changing block sizes during concurrent read operations. A kernel crash can lead to system instability, potential data loss, and downtime, affecting the reliability and availability of systems using affected Linux kernel versions.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is caused by a race condition between set_blocksize and read paths in the Linux kernel, which can lead to a kernel crash. Immediate mitigation involves applying the patch that truncates the page cache after flushing but before updating i_blksize, and locking out file IO and page faults during the update by taking both the i_rwsem and the invalidate_lock in exclusive mode for invalidations, and in shared mode for read/write operations. Therefore, updating the Linux kernel to a version that includes this fix is the recommended immediate step.