aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorIgor Matheus Andrade Torrente <[email protected]>2021-06-28 10:45:09 -0300
committerGreg Kroah-Hartman <[email protected]>2021-07-21 12:41:28 +0200
commit3b0c406124719b625b1aba431659f5cdc24a982c (patch)
treef31479e573eb234495f070a39caa8a041bedeaad /tools/perf/scripts/python/bin/stackcollapse-record
parent4fc2d3cd6d3a487a9fb79ebc81f7ae86a7dace7a (diff)
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. Cc: stable <[email protected]> # after 5.15-rc2 is out, give it time to bake Reported-and-tested-by: [email protected] Signed-off-by: Igor Matheus Andrade Torrente <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions