From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21772: partitions: mac: fix handling of bogus partition table
Date: Wed, 26 Feb 2025 18:17:28 -0800 [thread overview]
Message-ID: <2025022606-CVE-2025-21772-5ec0@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
partitions: mac: fix handling of bogus partition table
Fix several issues in partition probing:
- The bailout for a bad partoffset must use put_dev_sector(), since the
preceding read_part_sector() succeeded.
- If the partition table claims a silly sector size like 0xfff bytes
(which results in partition table entries straddling sector boundaries),
bail out instead of accessing out-of-bounds memory.
- We must not assume that the partition table contains proper NUL
termination - use strnlen() and strncmp() instead of strlen() and
strcmp().
The Linux kernel CVE team has assigned CVE-2025-21772 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.129 with commit 27a39d006f85e869be68c1d5d2ce05e5d6445bf5
Fixed in 6.6.79 with commit 92527100be38ede924768f4277450dfe8a40e16b
Fixed in 6.12.16 with commit 6578717ebca91678131d2b1f4ba4258e60536e9f
Fixed in 6.13.4 with commit 7fa9706722882f634090bfc9af642bf9ed719e27
Fixed in 6.14-rc3 with commit 80e648042e512d5a767da251d44132553fe04ae0
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-21772
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
block/partitions/mac.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/27a39d006f85e869be68c1d5d2ce05e5d6445bf5
https://git.kernel.org/stable/c/92527100be38ede924768f4277450dfe8a40e16b
https://git.kernel.org/stable/c/6578717ebca91678131d2b1f4ba4258e60536e9f
https://git.kernel.org/stable/c/7fa9706722882f634090bfc9af642bf9ed719e27
https://git.kernel.org/stable/c/80e648042e512d5a767da251d44132553fe04ae0
reply other threads:[~2025-02-27 2:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2025022606-CVE-2025-21772-5ec0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.