Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Authoritative record:CVE-2026-99007· Medium

Not known to be exploited · fixed in d510ed273854177f0a3ed330145858b2fe667f81 : update Linux kernel when convenient.

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 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d510ed273854177f0a3ed330145858b2fe667f81, 755c94d178b7e972bb766199d34e4ba4f63a89eb, 4e7b508c7c60dec7a86b7eb2a1b7e6d174afa457 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ca91a2758fcef6635626993557dd51cfbb6dd134, < d510ed273854177f0a3ed330145858b2fe667f81
Fixed in
  • d510ed273854177f0a3ed330145858b2fe667f81
LinuxLinuxAffected
  • ≥ ca91a2758fcef6635626993557dd51cfbb6dd134, < 755c94d178b7e972bb766199d34e4ba4f63a89eb
Fixed in
  • 755c94d178b7e972bb766199d34e4ba4f63a89eb
LinuxLinuxAffected
  • ≥ ca91a2758fcef6635626993557dd51cfbb6dd134, < 4e7b508c7c60dec7a86b7eb2a1b7e6d174afa457
Fixed in
  • 4e7b508c7c60dec7a86b7eb2a1b7e6d174afa457
LinuxLinuxAffected
  • ≥ ca91a2758fcef6635626993557dd51cfbb6dd134, < 4a2006c675758f0c765b36fec6b49d17e89159cf
Fixed in
  • 4a2006c675758f0c765b36fec6b49d17e89159cf
LinuxLinuxAffected
  • ≥ ca91a2758fcef6635626993557dd51cfbb6dd134, < 3b303696f61461b3569019d7fcac6a646652b2b4
Fixed in
  • 3b303696f61461b3569019d7fcac6a646652b2b4
LinuxLinuxAffected
  • =4.14
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set->mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper->fb and wire it into those mode_sets via drm_setup_crtcs_fb(). If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev->driver->fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper->deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set->fb == NULL, and nothing marks this fb_helper as needing a retry. __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper->deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -> drm_client_modeset_commit_atomic() -> __drm_atomic_helper_set_config(), which hits WARN_ON(!set->fb). Mark fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set->fb. The real error code is still returned to the caller unchanged.

References

Community reviews

Loading reviews…