From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/util-linux: security bump to 2.41.4
Date: Mon, 4 May 2026 16:48:08 +0200 [thread overview]
Message-ID: <20260504144808.11038-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260420142814.753135-1-buildroot@bubu1.eu>
In reply of:
> Security fixes:
>
> CVE-2026-27456 - mount(8) TOCTOU symlink attack via loop device.
> The SUID mount follows symlinks when resolving loop backing file
> paths. On systems where non-root users are permitted to mount loop
> devices (via 'user' option in fstab), this allows access to
> arbitrary files.
>
> CWE-190 - Integer overflow in libblkid parse_dos_extended().
> A crafted MBR disk image can cause uint32_t wraparound in EBR
> chain processing, causing reported partitions to not match the
> on-disk layout. Tools like udisks may then register a partition
> at logical sector 0.
>
> Full release notes: https://www.kernel.org/pub/linux/utils/util-linux/v2.41/v2.41.4-ReleaseNotes
>
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
Applied to 2026.02.x. Thanks
> ---
> package/util-linux/util-linux.hash | 2 +-
> package/util-linux/util-linux.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/util-linux/util-linux.hash b/package/util-linux/util-linux.hash
> index eab8a0c3b5..5a5656212c 100644
> --- a/package/util-linux/util-linux.hash
> +++ b/package/util-linux/util-linux.hash
> @@ -1,5 +1,5 @@
> # From https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.41/sha256sums.asc
> -sha256 3330d873f0fceb5560b89a7dc14e4f3288bbd880e96903ed9b50ec2b5799e58b util-linux-2.41.3.tar.xz
> +sha256 a8c213cc06048862602a42b2d299b340001f6d05c4407b549f3e03521df83688 util-linux-2.41.4.tar.xz
> # License files, locally calculated
> sha256 4c2db318192bda62f3f8fcf71488bb5e602ae4385eba281d711b46cc13a40bb3 README.licensing
> sha256 527f738966ca396cd5a68c1509390de2a780c6b614d9ee57f7544a6161938ed1 Documentation/licenses/COPYING.BSD-2-Clause
> diff --git a/package/util-linux/util-linux.mk b/package/util-linux/util-linux.mk
> index 7617041a46..1271bc7dc0 100644
> --- a/package/util-linux/util-linux.mk
> +++ b/package/util-linux/util-linux.mk
> @@ -8,7 +8,7 @@
> # util-linux-libs/util-linux-libs.mk needs to be updated accordingly as well.
>
> UTIL_LINUX_VERSION_MAJOR = 2.41
> -UTIL_LINUX_VERSION = $(UTIL_LINUX_VERSION_MAJOR).3
> +UTIL_LINUX_VERSION = $(UTIL_LINUX_VERSION_MAJOR).4
> UTIL_LINUX_SOURCE = util-linux-$(UTIL_LINUX_VERSION).tar.xz
> UTIL_LINUX_SITE = $(BR2_KERNEL_MIRROR)/linux/utils/util-linux/v$(UTIL_LINUX_VERSION_MAJOR)
>
> --
> 2.53.0
>
> _______________________________________________
> 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
prev parent reply other threads:[~2026-05-04 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 14:28 [Buildroot] [PATCH] package/util-linux: security bump to 2.41.4 Marcus Hoffmann via buildroot
2026-04-20 17:23 ` Julien Olivain via buildroot
2026-05-04 14:48 ` Thomas Perale 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=20260504144808.11038-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=buildroot@bubu1.eu \
--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