{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80960 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80960 is a 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-80960 and fix it if it is affected.\n\nWhat it is: CVE-2026-80960 is a 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-80960 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-80960/ (Markdown: https://insights.sbomify.com/CVE-2026-80960/index.md)","id":"CVE-2026-80960","markdown":"https://insights.sbomify.com/CVE-2026-80960/index.md","name":"CVE-2026-80960","record":{"aliases":["BELL-CVE-2026-80960","DEBIAN-CVE-2026-80960","GHSA-5phx-c495-rgx5","UBUNTU-CVE-2026-80960"],"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":"high_privilege","summary":"A local attacker with CAP_SYS_ADMIN can trigger an out-of-bounds write in the Linux kernel dm-pcache driver, 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":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm-pcache: validate on-media seg_num against the cache device size\n\nseg_num is read from the crc32c-only superblock, so whoever supplies the\ncache device on a table load (CAP_SYS_ADMIN) controls it. It sizes\ncache-\u003esegments[] and is the value every later on-media segment id is\nbounded against, yet it is never checked against the device. Because\ncache_dev-\u003emapping is the direct map of the pmem, CACHE_DEV_SEGMENT() for\na segment id past the device resolves to ordinary kernel memory beyond\nthe mapping; a new-cache init reaching such an id has cache_seg_init() -\u003e\ncache_dev_zero_range() memset() 12 KiB over that memory -- an\nout-of-bounds write into the kernel heap at table load. A zero seg_num\nmakes the segment allocations ZERO_SIZE_PTR.\n\nReject a seg_num that is zero, larger than the device can hold, or larger\nthan PCACHE_CACHE_SEGS_MAX before it is used.","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 on-media seg_num against the cache device size","id":"CVE-2026-80960","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-pcache: validate kset key_num and intra-segment bounds","id":"CVE-2026-80961"},"packages":[],"prev":{"headline":"dm-pcache: bound the persisted tail-position offset","id":"CVE-2026-80959"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"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 write in the Linux kernel dm-pcache driver, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-80960/"}