{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68235 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68235 is a vulnerability in Linux, published on 10 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-68235 and fix it if it is affected.\n\nWhat it is: CVE-2026-68235 is a vulnerability in Linux, published on 10 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-68235 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-68235/ (Markdown: https://insights.sbomify.com/CVE-2026-68235/index.md)","id":"CVE-2026-68235","markdown":"https://insights.sbomify.com/CVE-2026-68235/index.md","name":"CVE-2026-68235","record":{"aliases":["DEBIAN-CVE-2026-68235","GHSA-23xc-5vxv-wj6v","UBUNTU-CVE-2026-68235"],"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 null pointer dereference in the AMD display driver causes a kernel crash when connecting a second monitor via DisplayPort MST on specific hardware.","user_interaction":"required","vuln_class":"null_dereference"},"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/amd/display: dce100: skip non-DP stream encoders for DP MST\n\nOn DCE8-class ASICs (e.g. Bonaire), the resource pool contains digital\nDIG stream encoders plus one analog DAC encoder. When assigning a stream\nencoder for a second DisplayPort MST stream, if the preferred digital\nencoder is already acquired, dce100_find_first_free_match_stream_enc_for_link()\nfalls back to the first free pool entry. That entry may be the analog\nencoder, whose funcs table lacks DP hooks such as dp_set_stream_attribute.\nThe subsequent atomic commit then dereferences NULL function pointers in\nlink_set_dpms_on() and crashes.\n\nSkip encoders without dp_set_stream_attribute when the stream uses a DP\nsignal (including MST). Use dc_is_dp_signal(stream-\u003esignal) for the MST\nfallback path instead of checking only the link connector signal.\n\nTested on:\n- GPU: AMD Radeon R7 260X (Bonaire / DCE8)\n- Board: Supermicro C9X299-PG300\n- Setup: DP MST daisy chain, hotplug second monitor or have it connected on boot\n- Kernel: 7.1.3 (issue observed since 6.19)\n- Result: kernel oops without patch; dual monitors stable with patch\n\n(cherry picked from commit 28ec64943e3ee4d9b8d30cea61e380f1429953a8)","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/amd/display: dce100: skip non-DP stream encoders for DP MST","id":"CVE-2026-68235","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"drm/amd/display: set new_stream to NULL after release","id":"CVE-2026-68236"},"packages":[],"prev":{"headline":"drm/amdgpu: fix bo-\u003epin leaking in amdgpu_bo_create_reserved","id":"CVE-2026-68234"},"products":["Linux"],"published":"2026-08-10","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-18","vendors":["Linux"]},"summary":"A null pointer dereference in the AMD display driver causes a kernel crash when connecting a second monitor via DisplayPort MST on specific hardware.","url":"https://insights.sbomify.com/CVE-2026-68235/"}