Answer in brief
CVE-2025-37978 records a Medium severity (CVSS 5.5) vulnerability in block: integrity: Do not call set_page_dirty_lock(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=492c5d455969fc2e829f26ed4c83487b068f0dd7 <c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4 || >=492c5d455969fc2e829f26ed4c83487b068f0dd7 <9487fc1a10b3aa89feb24e7cedeccaaf63074617 || >=492c5d455969fc2e829f26ed4c83487b068f0dd7 <39e160505198ff8c158f11bce2ba19809a756e8b | c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4, 9487fc1a10b3aa89feb24e7cedeccaaf63074617, 39e160505198ff8c158f11bce2ba19809a756e8b |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
May 20, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.