From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH] package/udisks: security bump to version 2.11.1
Date: Sat, 14 Mar 2026 22:30:39 +0200 [thread overview]
Message-ID: <87h5qiqhlc.fsf@tarshish> (raw)
In-Reply-To: <20260306195347.8941-1-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Fri, 6 Mar 2026 20:53:47 +0100")
Hi Tomas,
On Fri, Mar 06 2026, Thomas Perale via buildroot wrote:
> In reply of:
>> This fixes these CVEs:
>> CVE-2026-26103:
>> https://github.com/storaged-project/udisks/security/advisories/GHSA-c75h-phf8-ccjm
>> CVE-2026-26104:
>> https://github.com/storaged-project/udisks/security/advisories/GHSA-fcvx-497g-6xmw
>>
>> Release notes:
>> https://github.com/storaged-project/udisks/releases/tag/udisks-2.11.1
>>
>> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
>
> Applied to 2025.11.x. Thanks
Not in 2025.11.x as of commit 0e13702babe60 ("package/libvips: fix
static build").
baruch
>
>> ---
>> package/udisks/udisks.hash | 2 +-
>> package/udisks/udisks.mk | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/package/udisks/udisks.hash b/package/udisks/udisks.hash
>> index a62e6b5ed6..8a70b90a67 100644
>> --- a/package/udisks/udisks.hash
>> +++ b/package/udisks/udisks.hash
>> @@ -1,3 +1,3 @@
>> # Locally calculated
>> -sha256 0bf30151fe8d9d2fb59b57f6630739dfbbd16417dee69ec57d43b37335bd649a udisks-2.11.0.tar.bz2
>> +sha256 e88c52bae02fa13414604bbef42c6bb91c2e24177ee0057ed55c6bd7451bcb6d udisks-2.11.1.tar.bz2
>> sha256 98046e932dc6c739001e79d7079a3bd958fc55475dcd917d27f884c0c93525cc COPYING
>> diff --git a/package/udisks/udisks.mk b/package/udisks/udisks.mk
>> index c9b66872e9..43d066c9e1 100644
>> --- a/package/udisks/udisks.mk
>> +++ b/package/udisks/udisks.mk
>> @@ -4,7 +4,7 @@
>> #
>> ################################################################################
>>
>> -UDISKS_VERSION = 2.11.0
>> +UDISKS_VERSION = 2.11.1
>> UDISKS_SOURCE = udisks-$(UDISKS_VERSION).tar.bz2
>> UDISKS_SITE = https://github.com/storaged-project/udisks/releases/download/udisks-$(UDISKS_VERSION)
>> UDISKS_LICENSE = GPL-2.0+
>> --
>> 2.47.3
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-03-14 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 19:49 [Buildroot] [PATCH] package/udisks: security bump to version 2.11.1 Giulio Benetti
2026-02-27 20:57 ` Julien Olivain via buildroot
2026-03-06 19:53 ` Thomas Perale via buildroot
2026-03-14 20:30 ` Baruch Siach via buildroot [this message]
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=87h5qiqhlc.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=giulio.benetti@benettiengineering.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