In the Linux kernel, the following vulnerability has been resolved: dm-pcache: validate kset key_num and intra-segment bounds Two more fields… (CVE-2026-80961)
A vulnerability in the Linux kernel's dm-pcache component allowed out-of-bounds reads due to insufficient validation of certain fields in cache device metadata. Specifically, the kset key_num and intra-segment offset and length were not properly bounded, leading to potential leakage of adjacent persistent memory to user space. This issue has been resolved by adding validation checks to ensure key_num and intra-segment bounds are within expected limits. The vulnerability affects only metadata supplied by cache devices with CAP_SYS_ADMIN privileges. Valid metadata remains unaffected.
AI Analysis
Technical Summary
The Linux kernel's dm-pcache module had a vulnerability where two fields decoded from the cache device metadata—key_num and intra-segment offset/length—were not properly validated. The key_num could exceed the PCACHE_KSET_KEYS_MAX buffer, causing reads past the buffer end before CRC comparison. Additionally, the intra-segment offset and length were used verbatim, allowing keys that run past their segment to be replayed into the cache tree, causing out-of-bounds reads that leak adjacent persistent memory into user space. Both fields are controlled by entities with CAP_SYS_ADMIN privileges. The fix involved adding the kset_onmedia_valid() function to bound key_num before any read and rejecting keys whose offset plus length exceed the segment data size.
Potential Impact
This vulnerability allows a privileged user (CAP_SYS_ADMIN) supplying the cache device to cause out-of-bounds reads in the kernel, potentially leaking adjacent persistent memory contents to user space. This could lead to unauthorized disclosure of sensitive information. The issue does not affect valid metadata and requires control over the cache device metadata.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to validate the kset key_num and intra-segment bounds before processing. Users should update to a kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel update from the vendor or distribution is the recommended remediation. No additional mitigations are indicated.
In the Linux kernel, the following vulnerability has been resolved: dm-pcache: validate kset key_num and intra-segment bounds Two more fields… (CVE-2026-80961)
Description
A vulnerability in the Linux kernel's dm-pcache component allowed out-of-bounds reads due to insufficient validation of certain fields in cache device metadata. Specifically, the kset key_num and intra-segment offset and length were not properly bounded, leading to potential leakage of adjacent persistent memory to user space. This issue has been resolved by adding validation checks to ensure key_num and intra-segment bounds are within expected limits. The vulnerability affects only metadata supplied by cache devices with CAP_SYS_ADMIN privileges. Valid metadata remains unaffected.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's dm-pcache module had a vulnerability where two fields decoded from the cache device metadata—key_num and intra-segment offset/length—were not properly validated. The key_num could exceed the PCACHE_KSET_KEYS_MAX buffer, causing reads past the buffer end before CRC comparison. Additionally, the intra-segment offset and length were used verbatim, allowing keys that run past their segment to be replayed into the cache tree, causing out-of-bounds reads that leak adjacent persistent memory into user space. Both fields are controlled by entities with CAP_SYS_ADMIN privileges. The fix involved adding the kset_onmedia_valid() function to bound key_num before any read and rejecting keys whose offset plus length exceed the segment data size.
Potential Impact
This vulnerability allows a privileged user (CAP_SYS_ADMIN) supplying the cache device to cause out-of-bounds reads in the kernel, potentially leaking adjacent persistent memory contents to user space. This could lead to unauthorized disclosure of sensitive information. The issue does not affect valid metadata and requires control over the cache device metadata.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to validate the kset key_num and intra-segment bounds before processing. Users should update to a kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel update from the vendor or distribution is the recommended remediation. No additional mitigations are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7hfq-329h-84pc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-80961"]
Threat ID: 6aa4a02f55bf5e2cf5a86b70
Added to database: 09/12/2026, 00:43:27 UTC
Last enriched: 09/12/2026, 01:25:17 UTC
Last updated: 09/12/2026, 02:21:38 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.