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().
Metrics
Affected Vendors & Products
References
History
Fri, 04 Jul 2025 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 22 May 2025 02:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Tue, 20 May 2025 17:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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(). | |
Title | block: integrity: Do not call set_page_dirty_lock() | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-05-20T16:58:21.422Z
Updated: 2025-05-26T05:24:58.426Z
Reserved: 2025-04-16T04:51:23.975Z
Link: CVE-2025-37978

No data.

Status : Awaiting Analysis
Published: 2025-05-20T17:15:48.423
Modified: 2025-05-21T20:24:58.133
Link: CVE-2025-37978
