CVE-2025-37978: Linux kernel · block: integrity: Do not call set_page_dirty_lock()
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 5 Nov 2026, 21:52 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 20 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel source code to remove the problematic call to set_page_dirty_lock() and adjust related function parameters. Users should update to the fixed kernel version once available. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel's block integrity subsystem involved improper use of set_page_dirty_lock() in interrupt context, which could cause kernel oopses. The issue arises when multiple protection information buffers share the same page, and the function set_page_dirty_lock() is called unnecessarily on pages not backed by files. The vulnerability has been resolved by removing the call to set_page_dirty_lock() and adjusting related function arguments.