{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68309 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68309 is a vulnerability in Linux, published on 16 Dec 2025. 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-2025-68309 and fix it if it is affected.\n\nWhat it is: CVE-2025-68309 is a vulnerability in Linux, published on 16 Dec 2025. 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-2025-68309 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-2025-68309/ (Markdown: https://insights.sbomify.com/CVE-2025-68309/index.md)","id":"CVE-2025-68309","markdown":"https://insights.sbomify.com/CVE-2025-68309/index.md","name":"CVE-2025-68309","record":{"aliases":["BELL-CVE-2025-68309","DEBIAN-CVE-2025-68309","GHSA-h3x8-qr26-4mxq","ROOT-OS-DEBIAN-13-CVE-2025-68309","ROOT-OS-UBUNTU-2204-CVE-2025-68309","ROOT-OS-UBUNTU-2404-CVE-2025-68309","UBUNTU-CVE-2025-68309"],"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 NULL pointer dereference in the Linux kernel PCI/AER subsystem can cause a kernel panic, 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\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u003exxx\nwill result in kernel panic. Fix 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":"PCI/AER: Fix NULL pointer access by aer_info","id":"CVE-2025-68309","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump","id":"CVE-2025-68310"},"packages":[],"prev":{"headline":"can: kvaser_usb: leaf: Fix potential infinite loop in command parsers","id":"CVE-2025-68308"},"products":["Linux"],"published":"2025-12-16","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-05-11","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Linux kernel PCI/AER subsystem can cause a kernel panic, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-68309/"}