{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80962 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80962 is a high-severity memory corruption 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-80962 and fix it if it is affected.\n\nWhat it is: CVE-2026-80962 is a high-severity memory corruption 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-80962 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-80962/ (Markdown: https://insights.sbomify.com/CVE-2026-80962/index.md)","id":"CVE-2026-80962","markdown":"https://insights.sbomify.com/CVE-2026-80962/index.md","name":"CVE-2026-80962","record":{"aliases":["BELL-CVE-2026-80962","DEBIAN-CVE-2026-80962","GHSA-mv2p-grx7-v5rf","UBUNTU-CVE-2026-80962"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker with CAP_SYS_ADMIN can trigger out-of-bounds memory access in the Linux kernel dm-pcache module via crafted on-disk metadata, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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 geometry fields from on-disk cache_info\n\ncache_segs_init() iterates cache_info-\u003en_segs times indexing\ncache-\u003esegments[], which is sized to the cache device geometry, and\nget_seg_id() takes each segment id from the on-media cache_info and the\nper-segment next_seg link. Both come from cache device metadata that is\nonly CRC-protected with a fixed public seed, so whoever supplies the\ncache device on a table load (CAP_SYS_ADMIN) controls them: an oversized\nn_segs or an out-of-range id drives an out-of-bounds access of\ncache-\u003esegments[] and a wild CACHE_DEV_SEGMENT() pointer into the device\nmapping -- an out-of-bounds read and write from on-disk data.\n\nReject an n_segs that exceeds the device segment count and a segment id\nthat is out of range before either is used. 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 geometry fields from on-disk cache_info","id":"CVE-2026-80962","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"dm-stats: fix a crash if allocation of per-cpu data fails","id":"CVE-2026-80963"},"packages":[],"prev":{"headline":"dm-pcache: validate kset key_num and intra-segment bounds","id":"CVE-2026-80961"},"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 out-of-bounds memory access in the Linux kernel dm-pcache module via crafted on-disk metadata, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-80962/"}