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/cups: security bump to v2.4.16
Date: Thu, 26 Feb 2026 16:46:46 +0100 [thread overview]
Message-ID: <87a4wvqzh5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260226084454.59339-1-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Thu, 26 Feb 2026 09:44:54 +0100")
>>>>> "Thomas" == Thomas Perale via buildroot <buildroot@buildroot.org> writes:
> For more information on the version bump, see:
> - https://github.com/OpenPrinting/cups/blob/v2.4.16/CHANGES.md
> - https://github.com/OpenPrinting/cups/releases/tag/v2.4.16
> - https://github.com/OpenPrinting/cups/releases/tag/v2.4.15
> Fixes the following vulnerabilities:
> - CVE-2025-58436:
> OpenPrinting CUPS is an open source printing system for Linux and
> other Unix-like operating systems. Prior to version 2.4.15, a client
> that connects to cupsd but sends slow messages, e.g. only one byte per
> second, delays cupsd as a whole, such that it becomes unusable by
> other clients.
> For more information, see
> - https://www.cve.org/CVERecord?id=CVE-2025-58436
> - https://github.com/OpenPrinting/cups/commit/40008d76a001babbb9beb9d9d74b01a86fb6ddb4
> - CVE-2025-61915:
> OpenPrinting CUPS is an open source printing system for Linux and
> other Unix-like operating systems. Prior to version 2.4.15, a user in
> the lpadmin group can use the cups web ui to change the config and
> insert a malicious line. Then the cupsd process which runs as root
> will parse the new config and cause an out-of-bound write.
> For more information, see
> - https://www.cve.org/CVERecord?id=CVE-2025-61915
> - https://github.com/OpenPrinting/cups/commit/db8d560262c22a21ee1e55dfd62fa98d9359bcb0
> 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:[~2026-02-26 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 8:44 [Buildroot] [PATCH] package/cups: security bump to v2.4.16 Thomas Perale via buildroot
2026-02-26 15:46 ` Peter Korsgaard [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=87a4wvqzh5.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