From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Olivier Schonken <olivier.schonken@gmail.com>
Subject: [Buildroot] [PATCH] package/cups: security bump to v2.4.16
Date: Thu, 26 Feb 2026 09:44:54 +0100 [thread overview]
Message-ID: <20260226084454.59339-1-thomas.perale@mind.be> (raw)
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>
---
package/cups/cups.hash | 2 +-
package/cups/cups.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/cups/cups.hash b/package/cups/cups.hash
index a200a82deb..7c08a68c10 100644
--- a/package/cups/cups.hash
+++ b/package/cups/cups.hash
@@ -1,4 +1,4 @@
# Locally calculated:
-sha256 660288020dd6f79caf799811c4c1a3207a48689899ac2093959d70a3bdcb7699 cups-2.4.14-source.tar.gz
+sha256 0339587204b4f9428dd0592eb301dec0bf9ea6ea8dce5d9690d56be585aba92d cups-2.4.16-source.tar.gz
sha256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30 LICENSE
sha256 977206f041b9a6f47ac00531e1242c0fab7063da71178f8d868b167b70866b6d NOTICE
diff --git a/package/cups/cups.mk b/package/cups/cups.mk
index e6de671174..d3e6094c67 100644
--- a/package/cups/cups.mk
+++ b/package/cups/cups.mk
@@ -4,7 +4,7 @@
#
################################################################################
-CUPS_VERSION = 2.4.14
+CUPS_VERSION = 2.4.16
CUPS_SOURCE = cups-$(CUPS_VERSION)-source.tar.gz
CUPS_SITE = https://github.com/OpenPrinting/cups/releases/download/v$(CUPS_VERSION)
CUPS_LICENSE = Apache-2.0 with GPL-2.0/LGPL-2.0 exception
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-02-26 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 8:44 Thomas Perale via buildroot [this message]
2026-02-26 15:46 ` [Buildroot] [PATCH] package/cups: security bump to v2.4.16 Peter Korsgaard
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=20260226084454.59339-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--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