From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Olivier Schonken <olivier.schonken@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/openjpeg: add patch to fix CVE-2025-54874
Date: Wed, 20 Aug 2025 16:45:54 +0200 [thread overview]
Message-ID: <87349mm4pp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250819133911.3965048-1-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Tue, 19 Aug 2025 15:39:11 +0200")
>>>>> "Thomas" == Thomas Perale via buildroot <buildroot@buildroot.org> writes:
> Fixes the following vulnerability:
> - CVE-2025-54874
> OpenJPEG is an open-source JPEG 2000 codec. In OpenJPEG 2.5.3 and
> earlier, a call to opj_jp2_read_header may lead to OOB heap memory
> write when the data stream p_stream is too short and p_image is not
> initialized.
> For more information, see:
> - https://www.cve.org/CVERecord?id=CVE-2025-54874
> - https://github.com/uclouvain/openjpeg/commit/f809b80c67717c152a5ad30bf06774f00da4fd2d
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-20 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 13:39 [Buildroot] [PATCH] package/openjpeg: add patch to fix CVE-2025-54874 Thomas Perale via buildroot
2025-08-20 14:45 ` Peter Korsgaard [this message]
2025-08-21 19:21 ` 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=87349mm4pp.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.org \
--cc=olivier.schonken@gmail.com \
--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