From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, "Raphaël Mélotte" <raphael.melotte@mind.be>
Subject: Re: [Buildroot] [PATCH] package/mupdf: add patch for CVE-2026-25556
Date: Sat, 28 Feb 2026 21:51:10 +0100 [thread overview]
Message-ID: <d6e061cbe4b8d14d857bc736abc5e961@free.fr> (raw)
In-Reply-To: <20260228201547.84699-1-thomas.perale@mind.be>
On 28/02/2026 21:15, Thomas Perale via buildroot wrote:
> Fixes the following vulnerability:
>
> - CVE-2026-25556:
> MuPDF versions 1.23.0 through 1.27.0 contain a double-free
> vulnerability in fz_fill_pixmap_from_display_list() when an
> exception
> occurs during display list rendering. The function accepts a
> caller-
> owned fz_pixmap pointer but incorrectly drops the pixmap in its
> error
> handling path before rethrowing the exception. Callers (including
> the
> barcode decoding path in fz_decode_barcode_from_display_list) also
> drop the same pixmap in cleanup, resulting in a double-free that
> can
> corrupt the heap and crash the process. This issue affects
> applications that enable and use MuPDF barcode decoding and can be
> triggered by processing crafted input that causes a rendering-time
> error while decoding barcodes.
>
> For more information, see
> - https://www.cve.org/CVERecord?id=CVE-2026-25556
> -
> https://cgit.ghostscript.com/cgi-bin/cgit.cgi/mupdf.git/commit/?id=d4743b6092d513321c23c6f7fe5cff87cde043c1
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-28 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 20:15 [Buildroot] [PATCH] package/mupdf: add patch for CVE-2026-25556 Thomas Perale via buildroot
2026-02-28 20:51 ` Julien Olivain via buildroot [this message]
2026-03-06 19:53 ` 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=d6e061cbe4b8d14d857bc736abc5e961@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=raphael.melotte@mind.be \
--cc=thomas.perale@mind.be \
/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