CVE-2025-37978

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().

A race condition in usbnet.c could lead to a use-after-free if linkwatch work is scheduled after the net device has been freed during disconnect. This can only be triggered by a privileged user with the ability to hot-unplug USB Ethernet interfaces or simulate link-reset events.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.