PT-2026-148149

CVE-2026-99305

·

Publicado

2026-11-16

·

Atualizado

2026-11-16

Descrição por

Pontuação
N/A
Não disponível

Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.

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)
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾