{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-98144 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98144 is a medium-severity memory corruption vulnerability in Linux kernel, published on 25 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-98144 and fix it if it is affected.\n\nWhat it is: CVE-2026-98144 is a medium-severity memory corruption vulnerability in Linux kernel, published on 25 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-98144 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-98144/ (Markdown: https://insights.sbomify.com/CVE-2026-98144/index.md)","id":"CVE-2026-98144","markdown":"https://insights.sbomify.com/CVE-2026-98144/index.md","name":"CVE-2026-98144","record":{"aliases":["BELL-CVE-2026-98144","DEBIAN-CVE-2026-98144","GHSA-qg8m-gr5q-xfg6","UBUNTU-CVE-2026-98144"],"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":"low_privilege","summary":"A local attacker can trigger a reference leak in the AMD XDNA driver by recycling buffer handles, potentially causing a denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/amdxdna: put the chained BO when its mapping fails\n\namdxdna_cmd_set_error() looks up the first BO of a command chain, which\ntakes a reference, and drops it at the end of the function. The mapping of\nthat BO is established in between, and the failure path returns without the\nput, so the reference is leaked.\n\nOrdinary use does not reach it. The chain has been submitted before any of\nthis runs, so aie2_cmdlist_fill_slot() has already called\namdxdna_cmd_get_op() on that BO and amdxdna_gem_vmap() has cached its\naddress. What makes it reachable is that the BO is resolved again by\nhandle here, and the handle is userspace's to recycle: closing it after\nsubmission and importing a dma-buf whose exporter implements no vmap onto\nthe same id leaves amdxdna_gem_get_obj() returning an object this cannot\nmap, since prime_import() types every import AMDXDNA_BO_SHARE.","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":"accel/amdxdna: put the chained BO when its mapping fails","id":"CVE-2026-98144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"accel/amdxdna: reject a command chain that carries no commands","id":"CVE-2026-98145"},"packages":[],"prev":{"headline":"accel: ethosu: Don't read the U65 rounding mode as a storage mode","id":"CVE-2026-98143"},"products":["Linux"],"published":"2026-09-25","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a reference leak in the AMD XDNA driver by recycling buffer handles, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-98144/"}