{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68429 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68429 is a vulnerability in Linux, published on 12 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-68429 and fix it if it is affected.\n\nWhat it is: CVE-2026-68429 is a vulnerability in Linux, published on 12 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-68429 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-68429/ (Markdown: https://insights.sbomify.com/CVE-2026-68429/index.md)","id":"CVE-2026-68429","markdown":"https://insights.sbomify.com/CVE-2026-68429/index.md","name":"CVE-2026-68429","record":{"aliases":["BELL-CVE-2026-68429","DEBIAN-CVE-2026-68429","GHSA-47qh-xgqx-2fv5","UBUNTU-CVE-2026-68429"],"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 race condition in the Linux kernel DP MST driver causes compositor crashes when connecting or disconnecting monitors, requiring local physical access.","user_interaction":"required","vuln_class":"race_condition"},"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/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()\n\nA hotplug or link-loss event can tear down the MST topology\n(setting mgr-\u003emst_state = false and mgr-\u003emst_primary = NULL) concurrently\nwith a caller invoking drm_dp_mst_topology_queue_probe(). Since the check\nis already performed under mgr-\u003elock, the condition is not a programming\nerror but a valid race -- the topology was valid when the caller decided\nto call this function, but was torn down before the lock was acquired.\n\nReplace the drm_WARN_ON() with a graceful early return. This eliminates\nspurious kernel warnings and the resulting compositor crashes observed\nwhen connecting/disconnecting DP MST monitors, while keeping the correct\nbehavior of doing nothing when MST is not active. A drm_dbg_mst() trace\nis added so the skipped probe remains observable under MST debug logging.\n\nThe existing WARN_ON(mgr-\u003emst_primary) in drm_dp_mst_topology_mgr_set_mst()\nalready catches the case where the topology is initialized twice, so no\ndiagnostic coverage is lost.","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/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()","id":"CVE-2026-68429","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"drm/amdgpu/gfx8: drop unecessary BUG_ON()","id":"CVE-2026-68430"},"packages":[],"prev":{"headline":"KVM: x86/mmu: Fix use-after-free on vendor module reload","id":"CVE-2026-68428"},"products":["Linux"],"published":"2026-08-12","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-17","vendors":["Linux"]},"summary":"A race condition in the Linux kernel DP MST driver causes compositor crashes when connecting or disconnecting monitors, requiring local physical access.","url":"https://insights.sbomify.com/CVE-2026-68429/"}