Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: block: integrity: Do not call set_page_dirty_lock() Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can't be called from interrupt context. Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec().
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.12.25 |
References
- https://git.kernel.org/stable/c/39e160505198ff8c158f11bce2ba19809a756e8bPatch
- https://git.kernel.org/stable/c/9487fc1a10b3aa89feb24e7cedeccaaf63074617Patch
- https://git.kernel.org/stable/c/c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4Patch
FAQ
What is CVE-2025-37978?
CVE-2025-37978 is a vulnerability with a CVSS score of 5.5 (MEDIUM). In the Linux kernel, the following vulnerability has been resolved: block: integrity: Do not call set_page_dirty_lock() Placing multiple protection information buffers inside the same page can lead ...
How severe is CVE-2025-37978?
CVE-2025-37978 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-37978?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.