Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98786drm/amd/display: guard dc_sink dereferences in MST mode validation

Description

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)

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 23 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f04d275d94e164d24516c32437c988a323018f63 – < 0189f725242087679bc9f1bbf77ad086f56a72c8
    • affected f04d275d94e164d24516c32437c988a323018f63 – < 5684a6c24c0d7c40ef2c4ccb3e4a64cffe76a791
    • affected f04d275d94e164d24516c32437c988a323018f63 – < daa0437fe5e451856aaf8fda602a9fc2105bbd54
    • affected f04d275d94e164d24516c32437c988a323018f63 – < 217f64f348c90cba62164e7ff38e0ccf78a5ca09
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.12.117 – ≤ 6.12.*
    • unaffected 6.18.61 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98786 badge
[![CVE-2026-98786](https://cveledger.app/badge/CVE-2026-98786.svg)](https://cveledger.app/cve/CVE-2026-98786)

Record last updated .