cbcvebase.
CVE-2024-26798
published 2024-04-04

CVE-2024-26798: In the Linux kernel, the following vulnerability has been resolved: fbcon: always restore the old font data in fbcon_do_set_font() Commit a5a923038d70 (fbdev…

PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.33%
25.2th percentile
In the Linux kernel, the following vulnerability has been resolved: fbcon: always restore the old font data in fbcon_do_set_font() Commit a5a923038d70 (fbdev: fbcon: Properly revert changes when vc_resize() failed) started restoring old font data upon failure (of vc_resize()). But it performs so only for user fonts. It means that the "system"/internal fonts are not restored at all. So in result, the very first call to fbcon_do_set_font() performs no restore at all upon failing vc_resize(). This can be reproduced by Syzkaller to crash the system on the next invocation of font_get(). It's rather hard to hit the allocation failure in vc_resize() on the first font_set(), but not impossible. Esp. if fault injection is used to aid the execution/failure. It was demonstrated by Sirius: BUG: unable to handle page fault for address: fffffffffffffff8 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD cb7b067 P4D cb7b067 PUD cb7d067 PMD 0 Oops: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 8007 Comm: poc Not tainted 6.7.0-g9d1694dc91ce #20 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:fbcon_get_font+0x229/0x800 drivers/video/fbdev/core/fbcon.c:2286 Call Trace: con_font_get drivers/tty/vt/vt.c:4558 [inline] con_font_op+0x1fc/0xf20 drivers/tty/vt/vt.c:4673 vt_k_ioctl drivers/tty/vt/vt_ioctl.c:474 [inline] vt_ioctl+0x632/0x2ec0 drivers/tty/vt/vt_ioctl.c:752 tty_ioctl+0x6f8/0x1570 drivers/tty/tty_io.c:2803 vfs_ioctl fs/ioctl.c:51 [inline] ... So restore the font data in any case, not only for user fonts. Note the later 'if' is now protected by 'old_userfont' and not 'old_data' as the latter is always set now. (And it is supposed to be non-NULL. Otherwise we would see the bug above again.)

Affected

20 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.82-1 (bookworm)linux 6.1.82-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux>= 5.15.64 < 5.15.1515.15.151
linuxlinux>= 5.19.6 < 5.205.20
linuxlinux>= 868749a7456dc48e93887a8474194e2ee6d6c21f < ae68f57df3335679653868fafccd8c88ef84ae98ae68f57df3335679653868fafccd8c88ef84ae98
linuxlinux>= a5a923038d70d2d4a86cb4e3f32625a5ee6e7e24 < 2f91a96b892fab2f2543b4a55740c5bee36b1a6b2f91a96b892fab2f2543b4a55740c5bee36b1a6b
linuxlinux>= a5a923038d70d2d4a86cb4e3f32625a5ee6e7e24 < 73a6bd68a1342f3a44cac9dffad81ad6a003e52073a6bd68a1342f3a44cac9dffad81ad6a003e520
linuxlinux>= a5a923038d70d2d4a86cb4e3f32625a5ee6e7e24 < a2c881413dcc5d801bdc9535e51270cc88cb9cd8a2c881413dcc5d801bdc9535e51270cc88cb9cd8
linuxlinux>= a5a923038d70d2d4a86cb4e3f32625a5ee6e7e24 < 00d6a284fcf3fad1b7e1b5bc3cd87cbfb60ce03f00d6a284fcf3fad1b7e1b5bc3cd87cbfb60ce03f
linuxlinux>= ebd6f886aa2447fcfcdce5450c9e1028e1d681bb < 20a4b5214f7bee13c897477168c77bbf79683c3d20a4b5214f7bee13c897477168c77bbf79683c3d
linuxlinux_kernel
linuxlinux_kernel>= 0 < 6.1.82-16.1.82-1
linuxlinux_kernel>= 0 < 6.7.9-16.7.9-1
linuxlinux_kernel>= 0 < 6.7.9-16.7.9-1
linuxlinux_kernel>= 0 < 5.15.0-112.1225.15.0-112.122
linuxlinux_kernel>= 5.15.64 < 5.15.1515.15.151
linuxlinux_kernel>= 6.0 < 6.1.816.1.81
linuxlinux_kernel>= 6.2 < 6.6.216.6.21
linuxlinux_kernel>= 6.7 < 6.7.96.7.9

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.0HIGH
vendor_ubuntu7.0HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.