mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-08-09 17:03:35 -09:00
fae66b0aa2
23.2.5 fixes the following security issues: 1) CVE-2024-31080: Heap buffer overread/data leakage in ProcXIGetSelectedEvents Introduced in: xorg-server-1.7.0 (2009) Fixed in: xorg-server-21.1.12 and xwayland-23.2.5 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/96798fc1967491c80a4d0 Found by: Alan Coopersmith of Oracle Solaris, while investigating https://debbugs.gnu.org/cgi/bugreport.cgi?bug=69762 The ProcXIGetSelectedEvents() function uses the byte-swapped length of the return data for the amount of data to return to the client, if the client has a different endianness than the X server. 2) CVE-2024-31081: Heap buffer overread/data leakage in ProcXIPassiveGrabDevice Introduced in: xorg-server-1.7.0 (2009) Fixed in: xorg-server-21.1.12 and xwayland-23.2.5 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/3e77295f888c67fc7645d Found by: Alan Coopersmith of Oracle Solaris The ProcXIPassiveGrabDevice() function uses the byte-swapped length of the return data for the amount of data to return to the client, if the client has a different endianness than the X server. 3) CVE-2024-31083: User-after-free in ProcRenderAddGlyphs Introduced in: prior to X11R6.7 (2004) Fixed in: xorg-server-21.1.12 and xwayland-23.2.5 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/bdca6c3d1f5057eeb3160 Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative The ProcRenderAddGlyphs() function calls the AllocateGlyph() function to store new glyphs sent by the client to the X server. AllocateGlyph() would return a new glyph with refcount=0 and a re-used glyph would end up not changing the refcount at all. The resulting glyph_new array would thus have multiple entries pointing to the same non-refcounted glyphs. ProcRenderAddGlyphs() may free a glyph, resulting in a use-after-free when the same glyph pointer is then later used. https://lists.x.org/archives/xorg-announce/2024-April/003497.html 24.1.4 fixes the following security issues: 1) CVE-2024-9632: Heap-based buffer overflow privilege escalation in _XkbSetCompatMap Introduced in: xorg-server-1.1.1 (2006) Fixed in: xorg-server-21.1.14 and xwayland-24.1.4 Fix:85b7765714Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative The _XkbSetCompatMap() function attempts to resize the `sym_interpret` buffer. However, It didn't update its size properly. It updated `num_si` only, without updating `size_si`. This may lead to local privilege escalation if the server is run as root or remote code execution (e.g. x11 over ssh). xorg-server-21.1.14 and xwayland-24.1.4 have been patched to fix this issue. https://lists.x.org/archives/xorg-announce/2024-October/003545.html 24.1.6 fixes the following security issues: 1) CVE-2025-26594: Use-after-free of the root cursor Introduced in: Unknown - Prior to X11R6.6 Xorg baseline Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/01642f26 https://gitlab.freedesktop.org/xorg/xserver/-/commit/b0a09ba6 Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative The root cursor is referenced in the xserver as a global variable. If a client manages to free the root cursor, the internal reference points to freed memory and causes a use-after-free. xorg-server-21.1.16 and xwayland-24.1.6 have been patched to fix this issue. 2) CVE-2025-26595: Buffer overflow in XkbVModMaskText() Introduced in: Prior to X11R6.1 Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/11fcda87 Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative The code in XkbVModMaskText() allocates a fixed sized buffer on the stack and copies the names of the virtual modifiers to that buffer. The code however fails to check the bounds of the buffer correctly and would copy the data regardless of the size, which may lead to a buffer overflow. xorg-server-21.1.16 and xwayland-24.1.6 have been patched to fix this issue. 3) CVE-2025-26596: Heap overflow in XkbWriteKeySyms() Introduced in: initial version of xc/programs/Xserver/xkb/xkb.c in X11R6 Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/80d69f01 Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative The computation of the length in XkbSizeKeySyms() differs from what is actually written in XkbWriteKeySyms(), which may lead to a heap based buffer overflow. xorg-server-21.1.16 and xwayland-24.1.6 have been patched to fix this issue. 4) CVE-2025-26597: Buffer overflow in XkbChangeTypesOfKey() Introduced in: X11R6.1 Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/0e4ed949 Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative If XkbChangeTypesOfKey() is called with 0 group, it will resize the key symbols table to 0 but leave the key actions unchanged. If later, the same function is called with a non-zero value of groups, this will cause a buffer overflow because the key actions are of the wrong size. 5) CVE-2025-26598: Out-of-bounds write in CreatePointerBarrierClient() Introduced in: xorg-server-1.14.0 Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/bba9df1a Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative The function GetBarrierDevice() searches for the pointer device based on its device id and returns the matching value, or supposedly NULL if no match was found. However the code will return the last element of the list if no matching device id was found which can lead to out of bounds memory access. 6) CVE-2025-26599: Use of uninitialized pointer in compRedirectWindow() Introduced in: Xorg 6.8.0. Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/c1ff84be https://gitlab.freedesktop.org/xorg/xserver/-/commit/b07192a8 Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative The function compCheckRedirect() may fail if it cannot allocate the backing pixmap. In that case, compRedirectWindow() will return a BadAlloc error without the validation of the window tree marked just before, which leaves the validate data partly initialized, and the use of an uninitialized pointer later. 7) CVE-2025-26600: Use-after-free in PlayReleasedEvents() Introduced in: X11R5 Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/6e0f332b Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative When a device is removed while still frozen, the events queued for that device remain while the device itself is freed and replaying the events will cause a use after free. 8) CVE-2025-26601: Use-after-free in SyncInitTrigger() Introduced in: X11R6 Fixed in: xorg-server-21.1.16 and xwayland-24.1.6 Fix: https://gitlab.freedesktop.org/xorg/xserver/-/commit/16a1242d https://gitlab.freedesktop.org/xorg/xserver/-/commit/f52cea2f https://gitlab.freedesktop.org/xorg/xserver/-/commit/8cbc90c8 https://gitlab.freedesktop.org/xorg/xserver/-/commit/c2857989 Found by: Jan-Niklas Sohn working with Trend Micro Zero Day Initiative When changing an alarm, the values of the change mask are evaluated one after the other, changing the trigger values as requested and eventually, SyncInitTrigger() is called. If one of the changes triggers an error, the function will return early, not adding the new sync object. This can be used to cause a use after free when the alarm eventually triggers. https://lists.x.org/archives/xorg-announce/2025-February/003584.html Drop now removed xwayland_eglstream option:701284f057Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Julien Olivain <ju.o@free.fr> (cherry picked from commit57d2bdb123) Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches