{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74699 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74699 is a memory corruption vulnerability in Linux, published on 22 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-74699 and fix it if it is affected.\n\nWhat it is: CVE-2026-74699 is a memory corruption vulnerability in Linux, published on 22 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-74699 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-74699/ (Markdown: https://insights.sbomify.com/CVE-2026-74699/index.md)","id":"CVE-2026-74699","markdown":"https://insights.sbomify.com/CVE-2026-74699/index.md","name":"CVE-2026-74699","record":{"aliases":["DEBIAN-CVE-2026-74699","GHSA-phjm-6f6w-c4wh","UBUNTU-CVE-2026-74699"],"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 memory leak in the Linux kernel's Xe GPU driver allows local attackers to exhaust system memory, potentially causing 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/xe: Fix memory leak in exec_queue_set_hang_replay_state()\n\nThe q-\u003ereplay_state is blindly overwritten, which can potentially leak\nmemory that was previously allocated by vmemdup_user().\nReturn an error if q-\u003ereplay_state is not empty.\n\nDiscovered using AI-assisted static analysis confirmed by Intel Product\nSecurity.\n\n(cherry picked from commit f6b6cc1118bdbc4265fa8b3bdf8565b26f13e56e)","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/xe: Fix memory leak in exec_queue_set_hang_replay_state()","id":"CVE-2026-74699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers","id":"CVE-2026-74700"},"packages":[],"prev":{"headline":"net/mlx5e: fix BQL reset on SQ re-activation","id":"CVE-2026-74698"},"products":["Linux"],"published":"2026-08-22","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-08-22","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's Xe GPU driver allows local attackers to exhaust system memory, potentially causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-74699/"}