{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80963 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80963 is a 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-80963 and fix it if it is affected.\n\nWhat it is: CVE-2026-80963 is a 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-80963 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-80963/ (Markdown: https://insights.sbomify.com/CVE-2026-80963/index.md)","id":"CVE-2026-80963","markdown":"https://insights.sbomify.com/CVE-2026-80963/index.md","name":"CVE-2026-80963","record":{"aliases":["AZL-100854","BELL-CVE-2026-80963","DEBIAN-CVE-2026-80963","GHSA-vfhr-8gq2-gpcv","UBUNTU-CVE-2026-80963"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A local attacker can cause a kernel crash via null pointer dereference in dm-stats when per-cpu data allocation fails.","user_interaction":"not_required","vuln_class":"null_dereference"},"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-stats: fix a crash if allocation of per-cpu data fails\n\nIf \"dm_kvzalloc(percpu_alloc_size, cpu_to_node(cpu))\" fails, the code\njumps to the \"out\" label and calls dm_stat_free. dm_stat_free does\n\"for_each_possible_cpu(cpu) { dm_kvfree(s-\u003estat_percpu[cpu][0].histogram,\ns-\u003ehistogram_alloc_size);\", which crashes with NULL pointer dereference\nif s-\u003estat_percpu[cpu] is NULL.\n\nThis commit fixes the bug by testing s-\u003estat_percpu[cpu] for NULL before\nusing it.","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-stats: fix a crash if allocation of per-cpu data fails","id":"CVE-2026-80963","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ALSA: virmidi: Check card index validity at probe","id":"CVE-2026-80964"},"packages":[],"prev":{"headline":"dm-pcache: validate geometry fields from on-disk cache_info","id":"CVE-2026-80962"},"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 can cause a kernel crash via null pointer dereference in dm-stats when per-cpu data allocation fails.","url":"https://insights.sbomify.com/CVE-2026-80963/"}