{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80822 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80822 is a vulnerability in Linux, published on 4 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-80822 and fix it if it is affected.\n\nWhat it is: CVE-2026-80822 is a vulnerability in Linux, published on 4 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-80822 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-80822/ (Markdown: https://insights.sbomify.com/CVE-2026-80822/index.md)","id":"CVE-2026-80822","markdown":"https://insights.sbomify.com/CVE-2026-80822/index.md","name":"CVE-2026-80822","record":{"aliases":["AZL-99686","BELL-CVE-2026-80822","DEBIAN-CVE-2026-80822","GHSA-ccq8-8x93-6cmr","UBUNTU-CVE-2026-80822"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A missing null check in the Microchip IPC SBI mailbox driver can cause a kernel crash if memory allocation fails, leading to denial of service.","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\nmailbox: mchp-ipc-sbi: Add null check for devm_kasprintf()\n\nAdd a check to see if devm_kasprintf() is not NULL in\nmchp_ipc_get_cluster_aggr_irq(), returning -ENOMEM if the function\nfailed.","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":"mailbox: mchp-ipc-sbi: Add null check for devm_kasprintf()","id":"CVE-2026-80822","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"nfc: st21nfca: validate ATR_REQ length against the received frame","id":"CVE-2026-80823"},"packages":[],"prev":{"headline":"nvmet: pci-epf: put CQ ref on create_cq mapping failure","id":"CVE-2026-80821"},"products":["Linux"],"published":"2026-09-04","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 missing null check in the Microchip IPC SBI mailbox driver can cause a kernel crash if memory allocation fails, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-80822/"}