{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98786 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98786 is a 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-98786 and fix it if it is affected.\n\nWhat it is: CVE-2026-98786 is a 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-98786 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-98786/ (Markdown: https://insights.sbomify.com/CVE-2026-98786/index.md)","id":"CVE-2026-98786","markdown":"https://insights.sbomify.com/CVE-2026-98786/index.md","name":"CVE-2026-98786","record":{"aliases":["AZL-109053","BELL-CVE-2026-98786","DEBIAN-CVE-2026-98786","GHSA-7r8j-xcf8-cxq6","UBUNTU-CVE-2026-98786"],"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 AMD display driver allows a local attacker to cause a denial of service via null pointer dereference during MST unplug.","user_interaction":"not_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: guard dc_sink dereferences in MST mode validation\n\ndm_dp_mst_is_port_support_mode() reads\naconnector-\u003edc_sink-\u003edsc_caps... for the DSC branch-throughput check,\nand get_conv_frl_bw()'s HDMI-PCON FRL-bandwidth path reads\naconnector-\u003edc_sink-\u003eedid_caps.max_frl_rate, both without a NULL\ncheck. dc_sink is cleared asynchronously on MST unplug, and both\nfunctions run from paths that the driver's own comments document as\nracing that teardown: the connector probe worker's -\u003emode_valid\ncallback and a compositor's atomic check, neither of which holds the\nMST manager lock that the teardown path uses. The former does have an\nexisting dsc_aux NULL check, but dsc_aux isn't reliably cleared in\nevery path that clears dc_sink, so it doesn't cover this.\n\nFail the port-support check and skip the FRL conversion path when the\nsink is already gone.\n\n(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)","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: guard dc_sink dereferences in MST mode validation","id":"CVE-2026-98786","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":"bpf: Fix missing migration protection in __rhtab_map_lookup_and_delete_batch()","id":"CVE-2026-98787"},"packages":[],"prev":{"headline":"drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend","id":"CVE-2026-98785"},"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-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel AMD display driver allows a local attacker to cause a denial of service via null pointer dereference during MST unplug.","url":"https://insights.sbomify.com/CVE-2026-98786/"}