Files
xserver/xkb
Olivier Fourdan 0e4ed94952 xkb: Fix buffer overflow in XkbChangeTypesOfKey()
If XkbChangeTypesOfKey() is called with nGroups == 0, it will resize the
key syms to 0 but leave the key actions unchanged.

If later, the same function is called with a non-zero value for nGroups,
this will cause a buffer overflow because the key actions are of the wrong
size.

To avoid the issue, make sure to resize both the key syms and key actions
when nGroups is 0.

CVE-2025-26597, ZDI-CAN-25683

This vulnerability was discovered by:
Jan-Niklas Sohn working with Trend Micro Zero Day Initiative

Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Part-of: <https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1828>
2025-02-25 11:43:01 +01:00
..
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2003-11-14 15:54:54 +00:00
2022-07-08 14:27:04 +00:00
2025-02-25 11:43:01 +01:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2017-10-30 13:45:20 -04:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2014-11-12 10:25:00 +10:00
2024-10-10 13:38:31 +00:00
2025-02-06 22:45:25 +00:00

The X server uses this directory to store the compiled version of the
current keymap and/or any scratch keymaps used by clients.  The X server
or some other tool might destroy or replace the files in this directory,
so it is not a safe place to store compiled keymaps for long periods of
time.  The default keymap for any server is usually stored in:
     X<num>-default.xkm
where <num> is the display number of the server in question, which makes
it possible for several servers *on the same host* to share the same 
directory.

Unless the X server is modified, sharing this directory between servers on
different hosts could cause problems.