VulnerabilityPublished 16 Sep 2026Updated 5 Oct 2026

CVE-2026-90035: Linux kernel · drm/amd/display: fix division by zero in get_estimated_bw()

Affects Linux kernelSource GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected 6.17.0-5.5 – 7.0.0-38.38 23 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected 6.17.0-1003.3 – 7.0.0-1017.17 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected 7.0.0-1003.3 – 7.0.0-1016.16 9 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 13 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected 7.0.0-1002.3 – 7.0.0-1008.9 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been implemented in the Linux kernel to add a guard against division by zero in the get_estimated_bw() function. Users should update to patched kernel versions to remediate this issue. Specific patched versions are not listed in the input data; therefore, users should consult their Linux distribution's security advisories for updates addressing CVE-2026-90035.

Description

A division by zero vulnerability was identified and fixed in the Linux kernel's AMD display driver component (drm/amd/display) in the get_estimated_bw() function. This occurs when a connected USB4/DPIA tunneling device reports an estimated bandwidth change before reporting a capability change, leading to a division by zero in an interrupt request path. The issue was addressed by adding a guard to prevent division by zero in the affected function.

Impact

The vulnerability can cause a division by zero error in the kernel's interrupt handler path, potentially leading to kernel crashes or instability when a USB4/DPIA tunneling device triggers the specific sequence of events. No known exploits in the wild have been reported.

Summary

The vulnerability in the Linux kernel's drm/amd/display driver involves the get_estimated_bw() function performing a division by link->dpia_bw_alloc_config.bw_granularity, which can be zero if the DP_TUNNELING_BW_ALLOC_CAP_CHANGED event has not yet been handled. The DPCD interrupt handler calls get_estimated_bw() when DP_TUNNELING_ESTIMATED_BW_CHANGED is set, regardless of whether the capability change event has occurred, causing a division by zero. The fix adds a guard to prevent division by zero, aligning with existing protections in related functions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2026, 21:07 UTC

Technical details

References

Community reviews

Related threats