tty: vt: initialize unicode screen buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d8ae7242718738ee1bf9bfdd632d2a4b150fdd26 · < e0ef23e9b0ad18b9fd3741b0f1ad2282e4a18def| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tty: vt: initialize unicode screen buffer
syzbot reports kernel infoleak at vcs_read() [1], for buffer can be read immediately after resize operation. Initialize buffer using kzalloc().
---------- #include <fcntl.h> #include <unistd.h> #include <sys/ioctl.h> #include <linux/fb.h>
int main(int argc, char *argv[]) { struct fb_var_screeninfo var = { }; const int fb_fd = open("/dev/fb0", 3); ioctl(fb_fd, FBIOGET_VSCREENINFO, &var); var.yres = 0x21; ioctl(fb_fd, FBIOPUT_VSCREENINFO, &var); return read(open("/dev/vcsu", O_RDONLY), &var, sizeof(var)) == -1; } ----------
From the CVE record · Linux
The Linux kernel virtual terminal code does not initialize the Unicode screen buffer after a resize. A local user who can resize the framebuffer and read /dev/vcsu may read kernel information from that buffer immediately afterward.
Engineers running Linux kernels with the affected virtual terminal code should check their systems; affected versions were not provided.