CVE-2025-37978

What it actually does

The vulnerability allows set_page_dirty_lock() to be invoked from interrupt context when multiple block integrity protection information buffers share a page, triggering kernel oopses because the function is unsafe in that context.

Why it matters to the business

Systems running affected Linux kernels may experience unexpected crashes or instability during I/O operations involving data integrity, leading to service disruptions and requiring reboots.

How an attack unfolds

An attacker triggers concurrent I/O paths that place multiple protection information buffers on the same page and invokes bio integrity handling from interrupt context; the unsafe dirty-page call then causes an oops. Related Linux kernel privilege-escalation campaigns have targeted similar kernel flaws.

How to fix it

Apply the upstream fix by updating to the Linux kernel commit c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4 or later stable releases that contain the change; rebuild and deploy the patched kernel across all affected systems.

How to confirm the fix worked

Verify the running kernel contains commit c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4, inspect the bio_integrity_unpin_bvec function to confirm removal of the set_page_dirty_lock call, and test integrity-enabled I/O workloads for stability.

Typical attack path

1. Identify a workload or driver that uses block integrity with multiple PI buffers sharing pages
2. Trigger I/O completion paths that execute from interrupt context
3. Cause set_page_dirty_lock() to be reached on a shared page
4. Induce kernel oops and potential denial of service or crash

How to detect it

Search kernel logs and dmesg output for oops or panic messages referencing bio_integrity, set_page_dirty_lock, or integrity unpin operations; correlate with workloads using DIF/DIX or similar block integrity mechanisms.

• bio_integrity_unpin_bvec
• set_page_dirty_lock
• protection information buffer page oops

What your security team should do

• Prioritize patching all production Linux systems to the fixed commit within the next maintenance window
• Monitor kernel oops and panic logs for signs of integrity-related crashes until patches are applied
• Review use of block integrity features and disable where not required to reduce attack surface