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-99007drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN

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.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 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.18% · top 93% 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 ca91a2758fcef6635626993557dd51cfbb6dd134 – < 423c871a586cff8b29f48db00e3c45c21d0e8121
    • affected ca91a2758fcef6635626993557dd51cfbb6dd134 – < e5f8f6e0f0a18c77c04b757d72319d897a0b4bc1
    • affected ca91a2758fcef6635626993557dd51cfbb6dd134 – < 9124411cb91b129ff3ffb0d723ecba7a5bf893f9
    • affected ca91a2758fcef6635626993557dd51cfbb6dd134 – < 4a2006c675758f0c765b36fec6b49d17e89159cf
    • affected ca91a2758fcef6635626993557dd51cfbb6dd134 – < 3b303696f61461b3569019d7fcac6a646652b2b4
    • affected ca91a2758fcef6635626993557dd51cfbb6dd134 – < 4e7b508c7c60dec7a86b7eb2a1b7e6d174afa457
    • affected ca91a2758fcef6635626993557dd51cfbb6dd134 – < d510ed273854177f0a3ed330145858b2fe667f81
    • affected ca91a2758fcef6635626993557dd51cfbb6dd134 – < 755c94d178b7e972bb766199d34e4ba4f63a89eb
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .