{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80961 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80961 is a high-severity vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80961 and fix it if it is affected.\n\nWhat it is: CVE-2026-80961 is a high-severity vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80961 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80961/ (Markdown: https://insights.sbomify.com/CVE-2026-80961/index.md)","id":"CVE-2026-80961","markdown":"https://insights.sbomify.com/CVE-2026-80961/index.md","name":"CVE-2026-80961","record":{"aliases":["BELL-CVE-2026-80961","DEBIAN-CVE-2026-80961","GHSA-7hfq-329h-84pc","UBUNTU-CVE-2026-80961"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel dm-pcache","requires_auth":"low_privilege","summary":"A local attacker with CAP_SYS_ADMIN can trigger an out-of-bounds read in the Linux kernel dm-pcache driver, leaking adjacent persistent memory to user space.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm-pcache: validate kset key_num and intra-segment bounds\n\nTwo more fields decoded from the cache device go unbounded. The kset\nkey_num drives cache_kset_crc() and the replay loop in cache_replay(),\nthe writeback worker and the GC worker, but only the magic and a\nfixed-seed CRC are checked first, so a non-last kset whose key_num exceeds\nthe PCACHE_KSET_KEYS_MAX buffer reads past its end before the CRC compare.\nA key's intra-segment offset and length in cache_key_decode() are taken\nverbatim, so a key running past its segment is replayed into the cache\ntree and the data CRC check and every later read hit then copy adjacent\npersistent memory into the caller's bio -- an out-of-bounds read that\nleaks to user space. Both fields are controlled by whoever supplies the\ncache device (CAP_SYS_ADMIN); the CRC seed is public.\n\nAdd kset_onmedia_valid() to bound key_num before any kset read, and\nreject a key whose offset plus length, computed in 64 bits, exceeds the\nsegment data_size. Valid metadata is unaffected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"dm-pcache: validate kset key_num and intra-segment bounds","id":"CVE-2026-80961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"dm-pcache: validate geometry fields from on-disk cache_info","id":"CVE-2026-80962"},"packages":[],"prev":{"headline":"dm-pcache: validate on-media seg_num against the cache device size","id":"CVE-2026-80960"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker with CAP_SYS_ADMIN can trigger an out-of-bounds read in the Linux kernel dm-pcache driver, leaking adjacent persistent memory to user space.","url":"https://insights.sbomify.com/CVE-2026-80961/"}