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-90035drm/amd/display: fix division by zero in get_estimated_bw()

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix division by zero in get_estimated_bw() get_estimated_bw() divides by link->dpia_bw_alloc_config.bw_granularity, which is zeroed by reset_bw_alloc_struct() and only populated once DP_TUNNELING_BW_ALLOC_CAP_CHANGED has been handled. link_dp_dpia_handle_bw_alloc_status(), the DPCD interrupt handler, calls get_estimated_bw() whenever DP_TUNNELING_ESTIMATED_BW_CHANGED is set, independently of whether DP_TUNNELING_BW_ALLOC_CAP_CHANGED has ever fired for that link. A connected USB4/DPIA tunneling device that reports an estimated-bandwidth change before ever reporting a capability change drives a division by zero in this IRQ path. link_dpia_send_bw_alloc_request() already guards the same bw_granularity division; add the identical guard here rather than introducing a new pattern. (cherry picked from commit f2a961457c33dc34223aad5c9e8971de34a4eed3)

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 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.19% · top 92% 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 8e5cfe547bf3beeb29d9608be68d22dff2b5012b – < 4c5b61b9df6ab33b55f228e1b6579cefad11a9f7
    • affected 8e5cfe547bf3beeb29d9608be68d22dff2b5012b – < ac2ab58a79bf2401ae8c5d1c030bf0a5a376f43a
    • affected 8e5cfe547bf3beeb29d9608be68d22dff2b5012b – < 4814f28c45f58a71a80d09b80a60da6a063b539a
    • affected 8e5cfe547bf3beeb29d9608be68d22dff2b5012b – < b08c3d5ee7feadd821208f7c2c1ec02a16ce5878
    • affected 8e5cfe547bf3beeb29d9608be68d22dff2b5012b – < f63de9054da858d57054474c32464106f8375e0d
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .