Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/xserver_xorg-server: security bump to version 21.1.10
Date: Mon, 1 Jan 2024 22:05:13 +0100	[thread overview]
Message-ID: <20240101220513.526090ad@windsurf> (raw)
In-Reply-To: <20231227162039.579880-1-peter@korsgaard.com>

On Wed, 27 Dec 2023 17:20:38 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:

> Fixes the following security issues:
> 
> 1) CVE-2023-6377: X.Org server: Out-of-bounds memory write in XKB button actions
> 
> A device has XKB button actions for each button on the device.  When a
> logical device switch happens (e.g.  moving from a touchpad to a mouse), the
> server re-calculates the information available on the respective master
> device (typically the Virtual Core Pointer).  This re-calculation only
> allocated enough memory for a single XKB action rather instead of enough for
> the newly active physical device's number of button.  As a result, querying
> or changing the XKB button actions results in out-of-bounds memory reads and
> writes.
> 
> This may lead to local privilege escalation if the server is run as root or
> remote code execution (e.g. x11 over ssh).
> 
> 2) CVE-2023-6478: X.Org server: Out-of-bounds memory read in
> RRChangeOutputProperty and RRChangeProviderProperty
> 
> This fixes an OOB read and the resulting information disclosure.
> 
> Length calculation for the request was clipped to a 32-bit integer.  With
> the correct stuff->nUnits value the expected request size was truncated,
> passing the REQUEST_FIXED_SIZE check.
> 
> The server then proceeded with reading at least stuff->nUnits bytes
> (depending on stuff->format) from the request and stuffing whatever it finds
> into the property.  In the process it would also allocate at least
> stuff->nUnits bytes, i.e.  4GB.
> 
> See also CVE-2022-46344 where this issue was fixed for other requests.
> 
> For more details, see the advisory:
> https://lists.x.org/archives/xorg-announce/2023-December/003435.html
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/x11r7/xserver_xorg-server/xserver_xorg-server.hash | 6 +++---
>  package/x11r7/xserver_xorg-server/xserver_xorg-server.mk   | 2 +-
>  2 files changed, 4 insertions(+), 4 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-01-01 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 16:20 [Buildroot] [PATCH] package/xserver_xorg-server: security bump to version 21.1.10 Peter Korsgaard
2024-01-01 21:05 ` Thomas Petazzoni via buildroot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240101220513.526090ad@windsurf \
    --to=buildroot@buildroot.org \
    --cc=peter@korsgaard.com \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox