Bug 2367625 (CVE-2025-37978) - CVE-2025-37978 kernel: block: integrity: Do not call set_page_dirty_lock()
Summary: CVE-2025-37978 kernel: block: integrity: Do not call set_page_dirty_lock()
Keywords:
Status: NEW
Alias: CVE-2025-37978
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-20 18:02 UTC by OSIDB Bzimport
Modified: 2025-05-21 03:59 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-20 18:02:22 UTC
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().

Comment 1 Avinash Hanwate 2025-05-21 03:52:18 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025052040-CVE-2025-37978-79b0@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.