VulnerabilityPublished 26 Oct 2026Updated 27 Oct 2026

CVE-2026-99007: Linux kernel · drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-99007· Medium

Not known to be exploited.

Data as of 28 Oct 2026, 01:58 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 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.10linux`pkg:deb/ubuntu/linux?arch=source&distro=stonking`Other threats	Affected 7.0.0-14.14 – 7.3.0-9.9 6 affected builds	Fixed in–
Ubuntu 26.10linux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonking`Other threats	Affected =7.0.0-1004.4 =7.3.0-1002.3 =7.3.0-1003.4	Fixed in–
Ubuntu 26.10linux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 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

No explicit patch links or vendor advisories are provided in the input. Users should monitor for updates to the linux-azure kernel and apply fixes when available.

Description

A vulnerability in the Linux kernel's drm/fb-helper subsystem causes improper handling of fbdev_probe() failures. When drm_fb_helper_single_fb_probe() fails with errors other than -EAGAIN, the system does not defer setup properly, leading to stale mode sets being committed and triggering kernel warnings. This issue affects specific linux-azure kernel versions and can cause instability in display mode setting operations.

Impact

This flaw can cause the Linux kernel to commit stale display mode settings, leading to kernel warnings and potential instability in graphics subsystem operations. It does not indicate direct privilege escalation or code execution but may affect system stability and display functionality in affected kernel versions.

Summary

The vulnerability in the Linux kernel drm/fb-helper code arises because drm_fb_helper_single_fb_probe() only defers setup on -EAGAIN errors. If fbdev_probe() fails with other errors, drm_setup_crtcs_fb() is not called and fb_helper->deferred_setup is not set. Consequently, mode_sets have modes and connectors but no framebuffer, and the restore function commits stale mode_sets causing WARN_ON(!set->fb). The fix involves marking fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure to prevent committing incomplete mode_sets until a successful re-probe occurs.

GCVE source: db.gcve.eu
OSV ID: UBUNTU-CVE-2026-99007
Osv Schema Version: 1.7.0
Ecosystems: Ubuntu:Pro:14.04:LTS, Ubuntu:Pro:16.04:LTS, Ubuntu:16.04:LTS, Ubuntu:Pro:18.04:LTS, Ubuntu:18.04:LTS, Ubuntu:Pro:FIPS-updates:18.04:LTS, Ubuntu:Pro:FIPS:18.04:LTS, Ubuntu:Pro:20.04:LTS, Ubuntu:20.04:LTS, Ubuntu:Pro:FIPS-updates:20.04:LTS, Ubuntu:Pro:FIPS:20.04:LTS, Ubuntu:22.04:LTS, Ubuntu:Nvidia-BlueField:22.04:LTS, Ubuntu:Pro:Realtime:22.04:LTS, Ubuntu:Pro:FIPS-preview:22.04:LTS, Ubuntu:Pro:FIPS-updates:22.04:LTS, Ubuntu:24.04:LTS, Ubuntu:Nvidia-BlueField:24.04:LTS, Ubuntu:Pro:Realtime:24.04:LTS, Ubuntu:Pro:FIPS-updates:24.04:LTS, Ubuntu:26.10, Ubuntu:26.04:LTS

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 01:58 UTC

Technical details

References

Community reviews

Related threats