{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72485 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72485 is a high-severity vulnerability in Linux, published on 15 Aug 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-72485 and fix it if it is affected.\n\nWhat it is: CVE-2026-72485 is a high-severity vulnerability in Linux, published on 15 Aug 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-72485 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-72485/ (Markdown: https://insights.sbomify.com/CVE-2026-72485/index.md)","id":"CVE-2026-72485","markdown":"https://insights.sbomify.com/CVE-2026-72485/index.md","name":"CVE-2026-72485","record":{"aliases":["BELL-CVE-2026-72485","DEBIAN-CVE-2026-72485","GHSA-cfj8-7wqc-c295","UBUNTU-CVE-2026-72485"],"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":"low_privilege","summary":"A null pointer dereference in the Linux kernel Coresight driver causes a system panic during probe failure, 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":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: platform: defer connection counter increment until alloc succeeds\n\ncoresight_add_out_conn() increments nr_outconns before calling\ndevm_krealloc_array() and again before devm_kmalloc(). If either\nallocation fails, the counter is already bumped while the corresponding\narray entry is NULL or uninitialized garbage.\n\ncoresight_add_in_conn() has the same problem with nr_inconns and\ndevm_krealloc_array().\n\nIn both cases the probe returns -ENOMEM, which causes\ncoresight_get_platform_data() to call coresight_release_platform_data()\nfor cleanup. That function iterates up to nr_outconns (or nr_inconns)\nentries and dereferences each pointer unconditionally, hitting the NULL\nor garbage entry and panicking instead of failing gracefully.\n\nFix by moving the counter increments to after all allocations succeed,\nso the struct is always consistent on any error path.","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: platform: defer connection counter increment until alloc succeeds","id":"CVE-2026-72485","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"mailbox: mtk-adsp: fix UAF during device teardown","id":"CVE-2026-72486"},"packages":[],"prev":{"headline":"staging: most: video: avoid double free on video register failure","id":"CVE-2026-72484"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-03","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel Coresight driver causes a system panic during probe failure, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-72485/"}