CVE-2025-38302
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-11-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves improper use of the function submit_bio_noacct_nocheck within blk_zone_wplug_bio_work. Bios (block I/O operations) that are queued in the zone write plug have already undergone all necessary preparation, including freeze protection, in the submit_bio path. Using submit_bio_noacct_nocheck again duplicates this work and can cause deadlocks when freezing a queue with pending bio write plugs. The fix is to bypass the redundant freeze protection and checks by submitting bios directly through submit_bio or blk_mq_submit_bio.
How can this vulnerability impact me? :
This vulnerability can cause deadlocks in the Linux kernel's block I/O subsystem when freezing queues with pending bio write plugs. Such deadlocks may lead to system hangs or degraded performance, potentially impacting system stability and availability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that the Linux kernel is updated to a version where the fix is applied. The fix involves avoiding the use of submit_bio_noacct_nocheck in blk_zone_wplug_bio_work and instead using submit_bio or blk_mq_submit_bio to prevent deadlocks caused by duplicate freeze protection and checks.