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().
Product status
492c5d455969fc2e829f26ed4c83487b068f0dd7 (git) before c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4
492c5d455969fc2e829f26ed4c83487b068f0dd7 (git) before 9487fc1a10b3aa89feb24e7cedeccaaf63074617
492c5d455969fc2e829f26ed4c83487b068f0dd7 (git) before 39e160505198ff8c158f11bce2ba19809a756e8b
6.8
Any version before 6.8
6.12.25 (semver)
6.14.4 (semver)
6.15 (original_commit_for_fix)
References
git.kernel.org/...c/c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4
git.kernel.org/...c/9487fc1a10b3aa89feb24e7cedeccaaf63074617
git.kernel.org/...c/39e160505198ff8c158f11bce2ba19809a756e8b