Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/xlib_libXpm: security bump to version 3.5.19
Date: Wed, 06 May 2026 22:38:03 +0200	[thread overview]
Message-ID: <fcf01491a790ae04cdf6b5dbe13d15ac@free.fr> (raw)
In-Reply-To: <20260506190239.655752-1-peter@korsgaard.com>

On 06/05/2026 21:02, Peter Korsgaard wrote:
> Fixes the following vulnerability:
> 
> CVE-2026-4367: libXpm Out-of-bounds read in xpmNextWord()
> 
> libXpm uses a number of internal helper functions to parse the XPM file
> format.
> One of these internal functions, xpmNextString(), checks for the NULL
> terminator when looking for the end of the current string but not when
> looking for the beginning of the next string.
> A small XPM file with a malformed color table definition may cause the
> function xpmNextWord(), called from xpmParseColors() following a call 
> to
> xpmNextString(), to start past the actual end of the file, causing an
> out-of-bound read.
> 
> Advisory:
> https://lists.x.org/archives/xorg-announce/2026-April/003690.html
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-05-06 20:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 19:02 [Buildroot] [PATCH] package/xlib_libXpm: security bump to version 3.5.19 Peter Korsgaard
2026-05-06 20:38 ` Julien Olivain via buildroot [this message]
2026-05-15 17:46 ` Thomas Perale via buildroot

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=fcf01491a790ae04cdf6b5dbe13d15ac@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=peter@korsgaard.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