{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98779 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98779 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98779 and fix it if it is affected.\n\nWhat it is: CVE-2026-98779 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98779 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-98779/ (Markdown: https://insights.sbomify.com/CVE-2026-98779/index.md)","id":"CVE-2026-98779","markdown":"https://insights.sbomify.com/CVE-2026-98779/index.md","name":"CVE-2026-98779","record":{"aliases":["AZL-109334","BELL-CVE-2026-98779","DEBIAN-CVE-2026-98779","GHSA-7q7p-f6vv-qrwf","UBUNTU-CVE-2026-98779"],"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 memory leak in the AMD GPU driver's ACP initialization failure path can lead to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\ndrm/amdgpu: fix ACP MFD device leak on init failure\n\nacp_hw_init() registers ACP child devices with mfd_add_devices() before\nattaching them to the ACP power domain and initializing the hardware.\n\nIf attaching a child to the power domain fails, or if the ACP reset or\nclock enable operation times out, the failure path frees only the\nsource cell, resource, and platform-data allocations. The child\nplatform devices already registered by mfd_add_devices() remain\nregistered and are never released.\n\nRemove the children from the power domain and unregister the MFD\ndevices on failures that occur after mfd_add_devices() succeeds. Keep\nmfd_add_devices() failures on the existing cleanup path since the MFD\ncore already rolls back partially registered children itself.\n\nThe issue was identified by a static analysis tool I developed and\nconfirmed by manual review.\n\n(cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)","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":"drm/amdgpu: fix ACP MFD device leak on init failure","id":"CVE-2026-98779","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"drm/amdgpu: fix IP instance memory leak on kobject add failure","id":"CVE-2026-98780"},"packages":[],"prev":{"headline":"binder: fix is_failure flag for superseded transaction cleanup","id":"CVE-2026-98778"},"products":["Linux"],"published":"2026-10-18","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-21","vendors":["Linux"]},"summary":"A memory leak in the AMD GPU driver's ACP initialization failure path can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-98779/"}