block: integrity: Do not call set_page_dirty_lock()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.256.14.46.15In 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().
From the CVE record · Linux
The Linux kernel’s block integrity code can oops when multiple protection information buffers occupy the same page and set_page_dirty_lock() is called from interrupt context. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified.