aboutsummaryrefslogtreecommitdiff
path: root/nx-X11/programs/Xserver/xkb
diff options
context:
space:
mode:
authorMike Gabriel <mike.gabriel@das-netzwerkteam.de>2015-02-10 19:17:58 +0100
committerMike Gabriel <mike.gabriel@das-netzwerkteam.de>2015-02-10 19:40:48 +0100
commit471223907081355a288a315b33a2b70eb4c8fb1e (patch)
tree626691f6936497709863d91e7b0851be08468e86 /nx-X11/programs/Xserver/xkb
parent223f5548b70910a2d745b7b48d2096f29b560def (diff)
downloadnx-libs-471223907081355a288a315b33a2b70eb4c8fb1e.tar.gz
nx-libs-471223907081355a288a315b33a2b70eb4c8fb1e.tar.bz2
nx-libs-471223907081355a288a315b33a2b70eb4c8fb1e.zip
Avoid large pixmaps (110_nxagent_createpixmap-bounds-check.full.patch).
It is allowed to try and allocate a pixmap which is larger than 32767 in either dimension. However, all of the framebuffer code is buggy and does not reliably draw to such big pixmaps, basically because the Region data structure operates with signed shorts for the rectangles in it. Furthermore, several places in the X server computes the size in bytes of the pixmap and tries to store it in an integer. This integer can overflow and cause the allocated size to be much smaller. So, such big pixmaps are rejected here with a BadAlloc Originally contributed by FreeNX Team
Diffstat (limited to 'nx-X11/programs/Xserver/xkb')
0 files changed, 0 insertions, 0 deletions