Skip to content
Threat Brief

← All advisories

CVE-2026-99305

High 7.8No known exploitationFix available

fbdev: udlfb: don't rebuild the mode list while the framebuffer is in use

Record last updated

CVSS score

7.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.1%

Higher than 2% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: fbdev: udlfb: don't rebuild the mode list while the framebuffer is in use dlfb_setup_modes() frees info->modelist with fb_destroy_modelist() and rebuilds it, but fbcon holds raw pointers into that list in fb_display[i].mode and nothing un-publishes them the way do_unregister_framebuffer() and store_modes() do with fbcon_delete_modelist(). The function does refuse to install a new mode while the framebuffer has users (dlfb->fb_count != 0), but only after the list is already destroyed. Reached from the 0666 "edid" sysfs attribute, an unprivileged write to /sys/class/graphics/fb0/edid therefore fails with -EINVAL and still leaves every fb_display[i].mode dangling; the next console switch reads the freed fb_videomode in fb_videomode_to_var(). Test fb_count before touching the list. fbcon takes a reference through fbcon_open(), so that condition covers exactly the states in which fb_display[] points into the list, and the errno returned to userspace is unchanged. BUG: KASAN: slab-use-after-free in fb_videomode_to_var (drivers/video/fbdev/core/modedb.c:905) Read of size 4 at addr ffff8880107b449c by task kworker/1:1/47 Workqueue: events console_callback Call Trace: fb_videomode_to_var (drivers/video/fbdev/core/modedb.c:905) display_to_var (drivers/video/fbdev/core/fbcon.c:998) fbcon_switch (drivers/video/fbdev/core/fbcon.c:2182) redraw_screen (drivers/tty/vt/vt.c:994) complete_change_console (drivers/tty/vt/vt_ioctl.c:1141) console_callback (drivers/tty/vt/vt.c:3358) process_one_work (kernel/workqueue.c:3396) worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) ... The buggy address is located 28 bytes inside of freed 96-byte region [ffff8880107b4480, ffff8880107b44e0)

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 7d9485e2c53caaaed9606a39de1c2746cc9ba262 before ac9cfa552102b8e80e88c2872e80dc9cb5f07ddaac9cfa552102b8e80e88c2872e80dc9cb5f07ddaCVE Program
LinuxLinuxfrom 7d9485e2c53caaaed9606a39de1c2746cc9ba262 before 291010d5de1c9efc38e98c416b6230500bfae438291010d5de1c9efc38e98c416b6230500bfae438CVE Program
LinuxLinuxfrom 7d9485e2c53caaaed9606a39de1c2746cc9ba262 before 1e13b8957510cfbc7367b3be1f08adc1757bb6d41e13b8957510cfbc7367b3be1f08adc1757bb6d4CVE Program
LinuxLinuxfrom 7d9485e2c53caaaed9606a39de1c2746cc9ba262 before 4bc608af98a3da0fa0b17af67a64d0d11d625a1d4bc608af98a3da0fa0b17af67a64d0d11d625a1dCVE Program
LinuxLinux2.6.34Not documentedCVE Program
Microsoftazl3 kernel 6.6.161.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0Not documented0:6.18.62-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 2.6.34Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references