Skip to content
statance
MenuClose
unknown

CVE-2026-98786

drm/amd/display: guard dc_sink dereferences in MST mode validation

Published 18 Oct 2026 · Source updated 10 Nov 2026 · Retrieved 2026-11-19 07:21 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: guard dc_sink dereferences in MST mode validation

dm_dp_mst_is_port_support_mode() reads aconnector->dc_sink->dsc_caps... for the DSC branch-throughput check, and get_conv_frl_bw()'s HDMI-PCON FRL-bandwidth path reads aconnector->dc_sink->edid_caps.max_frl_rate, both without a NULL check. dc_sink is cleared asynchronously on MST unplug, and both functions run from paths that the driver's own comments document as racing that teardown: the connector probe worker's ->mode_valid callback and a compositor's atomic check, neither of which holds the MST manager lock that the teardown path uses. The former does have an existing dsc_aux NULL check, but dsc_aux isn't reliably cleared in every path that clears dc_sink, so it doesn't cover this.

Fail the port-support check and skip the FRL conversion path when the sink is already gone.

(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: f04d275d94e164d24516c32437c988a323018f63 to < 0189f725242087679bc9f1bbf77ad086f56a72c8; affected: f04d275d94e164d24516c32437c988a323018f63 to < 5684a6c24c0d7c40ef2c4ccb3e4a64cffe76a791; affected: f04d275d94e164d24516c32437c988a323018f63 to < daa0437fe5e451856aaf8fda602a9fc2105bbd54; affected: f04d275d94e164d24516c32437c988a323018f63 to < 217f64f348c90cba62164e7ff38e0ccf78a5ca09See vendor advisory
LinuxLinuxaffected: 6.0; unaffected: 0 to < 6.0; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.2.10 to ≤ 7.2.*; unaffected: 7.3 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed