{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40060 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40060 is a vulnerability in Linux, published on 28 Oct 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-40060 and fix it if it is affected.\n\nWhat it is: CVE-2025-40060 is a vulnerability in Linux, published on 28 Oct 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-40060 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-40060/ (Markdown: https://insights.sbomify.com/CVE-2025-40060/index.md)","id":"CVE-2025-40060","markdown":"https://insights.sbomify.com/CVE-2025-40060/index.md","name":"CVE-2025-40060","record":{"aliases":["BELL-CVE-2025-40060","DEBIAN-CVE-2025-40060","GHSA-8w6p-wg52-cjgx","ROOT-OS-DEBIAN-12-CVE-2025-40060","ROOT-OS-DEBIAN-13-CVE-2025-40060","ROOT-OS-UBUNTU-2204-CVE-2025-40060","ROOT-OS-UBUNTU-2404-CVE-2025-40060","UBUNTU-CVE-2025-40060"],"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 missing NULL check in the Linux kernel TRBE driver causes a kernel panic on allocation failure, leading to local 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\ncoresight: trbe: Return NULL pointer for allocation failures\n\nWhen the TRBE driver fails to allocate a buffer, it currently returns\nthe error code \"-ENOMEM\". However, the caller etm_setup_aux() only\nchecks for a NULL pointer, so it misses the error. As a result, the\ndriver continues and eventually causes a kernel panic.\n\nFix this by returning a NULL pointer from arm_trbe_alloc_buffer() on\nallocation failures. This allows that the callers can properly handle\nthe failure.","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":"coresight: trbe: Return NULL pointer for allocation failures","id":"CVE-2025-40060","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"RDMA/rxe: Fix race in do_task() when draining","id":"CVE-2025-40061"},"packages":[],"prev":{"headline":"coresight: Fix incorrect handling for return value of devm_kzalloc","id":"CVE-2025-40059"},"products":["Linux"],"published":"2025-10-28","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 missing NULL check in the Linux kernel TRBE driver causes a kernel panic on allocation failure, leading to local denial of service.","url":"https://insights.sbomify.com/CVE-2025-40060/"}