{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.113-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.11-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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-\u003emode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper-\u003efb 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-\u003edriver-\u003efbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper-\u003edeferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set-\u003efb == NULL, and nothing marks this fb_helper as needing a retry.  __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper-\u003edeferred_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() -\u003e drm_client_modeset_commit_atomic() -\u003e __drm_atomic_helper_set_config(), which hits WARN_ON(!set-\u003efb).  Mark fb_helper-\u003edeferred_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-\u003efb. The real error code is still returned to the caller unchanged.",
  "id": "DEBIAN-CVE-2026-99007",
  "modified": "2026-10-24T05:47:29.776806612Z",
  "published": "2026-10-23T13:17:23.157Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99007"
    }
  ],
  "upstream": [
    "CVE-2026-99007"
  ]
}