CVE-2026-99305 · Runtime
NO FIX YET · SEE WHAT TO DO
Writing to the framebuffer's EDID sysfs attribute in the udlfb driver frees the mode list while the console still points into it, causing a use-after-free on the next console switch. The sources describe a kernel memory-safety bug that can read freed memory and could crash the system or corrupt data.
first public Nov 16, 2026 · 3 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Linux machines running the udlfb framebuffer driver with a DisplayLink USB 2.0 graphics adapter attached. An unprivileged write to /sys/class/graphics/fb0/edid frees the mode list while fbcon still points into it, and the next console switch reads freed memory (KASAN use-after-free). Systems without udlfb or a DisplayLink device can skip it.
Not affected if no-displaylink-device, no-displaylink-hardware, udlfb-not-loaded
Who cares displaylink, fbdev, linux-kernel, udlfb, use-after-free
lsmod | grep udlfb and ls /sys/class/graphics/fb*/edid (the edid sysfs attribute is mode 0666)if (dlfb->fb_count) check in dlfb_setup_modes in drivers/video/fbdev/udlfb.cIn 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)
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.