fbdev: fbcon: fix out-of-bounds read in err_out of fbcon_do_set_font()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a5a923038d70d2d4a86cb4e3f32625a5ee6e7e24 · < 076b1aa65f77a49bce5a48a4a55a397cfcafa2b8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fbdev: fbcon: fix out-of-bounds read in err_out of fbcon_do_set_font()
When fbcon_do_set_font() fails (e.g., due to a memory allocation failure inside vc_resize() under heavy memory pressure), it jumps to the `err_out` label to roll back the console state. However, the current rollback logic forgets to restore the `hi_font` state, leading to a severe state machine corruption.
Earlier in the function, `set_vc_hi_font()` might be called to change `vc->vc_hi_font_mask` and mutate the screen buffer. If `vc_resize()` subsequently fails, the `err_out` path restores `vc_font.charcount` but entirely skips rolling back the `vc_hi_font_mask` and the screen buffer.
This mismatch leaves the terminal in a desynchronized state. Because `vc_hi_font_mask` remains set, the VT subsystem will still accept character indices greater than 255 from userspace and write them to the screen buffer. Subsequent rendering calls (e.g., `fbcon_putcs()`) will then use these inflated indices to access the reverted, 256-character font array, leading to a deterministic out-of-bounds read and potential kernel memory disclosure.
Fix this by adding the missing rollback logic for the `hi_font` mask and screen buffer in the error path.
From the CVE record · Linux
The Linux kernel’s fbcon font-setting error path can leave the console’s font state inconsistent if a resize fails, such as under heavy memory pressure. Subsequent userspace character writes to the virtual terminal can trigger an out-of-bounds read during rendering, potentially disclosing kernel memory; the input does not specify authentication requirements.
Engineers running Linux kernels with fbcon should check whether their kernel includes the fix; affected versions are not specified.