tty: Fix out-of-bound vmalloc access in imageblit
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < d570c48dd37dbe8fc6875d4461d01a9554ae2560| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tty: Fix out-of-bound vmalloc access in imageblit
This issue happens when a userspace program does an ioctl FBIOPUT_VSCREENINFO passing the fb_var_screeninfo struct containing only the fields xres, yres, and bits_per_pixel with values.
If this struct is the same as the previous ioctl, the vc_resize() detects it and doesn't call the resize_screen(), leaving the fb_var_screeninfo incomplete. And this leads to the updatescrollmode() calculates a wrong value to fbcon_display->vrows, which makes the real_y() return a wrong value of y, and that value, eventually, causes the imageblit to access an out-of-bound address value.
To solve this issue I made the resize_screen() be called even if the screen does not need any resizing, so it will "fix and fill" the fb_var_screeninfo independently.
From the CVE record · Linux
The Linux kernel framebuffer imageblit path can access memory out of bounds when a local userspace program passes an incomplete fb_var_screeninfo structure through the FBIOPUT_VSCREENINFO ioctl. If the values match the previous ioctl, the screen resize is skipped, leaving fields incomplete and causing an incorrect address calculation.
Engineers running the Linux kernel should check their deployments; affected versions were not provided.