From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-52992: fs/adfs: validate nzones in adfs_validate_bblk()
Date: Wed, 24 Jun 2026 17:30:16 +0100 [thread overview]
Message-ID: <2026062444-CVE-2026-52992-af99@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fs/adfs: validate nzones in adfs_validate_bblk()
Reject ADFS disc records with a zero zone count during boot block
validation, before the disc record is used.
When nzones is 0, adfs_read_map() passes it to kmalloc_array(0, ...)
which returns ZERO_SIZE_PTR, and adfs_map_layout() then writes to
dm[-1], causing an out-of-bounds write before the allocated buffer.
adfs_validate_dr0() already rejects nzones != 1 for old-format
images. Add the equivalent check to adfs_validate_bblk() for
new-format images so that a crafted image with nzones == 0 is
rejected at probe time.
Found by syzkaller.
The Linux kernel CVE team has assigned CVE-2026-52992 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 5.10.258 with commit 33aafd2418a59c96c0389d47ea09026661fa9ec6
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 5.15.209 with commit 1f0ed0f57f0fc87e46fe19a05435c214dc464be2
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 6.1.175 with commit 6ff8cca5cdb4f2e0ea6d28ecd78479dd3f221ebc
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 6.6.141 with commit a11372a8b1ceaa5e950a84b3b5fbf8228f25e277
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 6.12.91 with commit 1586bd2d2fb436a26df20a70e78b000d34a7d159
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 6.18.33 with commit a3fd5dc1c7b0aae947a67dc2e2c037d57557a4de
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 7.0.10 with commit 60d82592ac8b5637fbed871381eb0a16df0a492e
Issue introduced in 5.6 with commit f6f14a0d71b0773a1d4147d1a3c33d537cd213ab and fixed in 7.1 with commit dd9d3e16c2d5fa166e13dce07413be51f42c8f5d
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-2026-52992
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:
fs/adfs/super.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/33aafd2418a59c96c0389d47ea09026661fa9ec6
https://git.kernel.org/stable/c/1f0ed0f57f0fc87e46fe19a05435c214dc464be2
https://git.kernel.org/stable/c/6ff8cca5cdb4f2e0ea6d28ecd78479dd3f221ebc
https://git.kernel.org/stable/c/a11372a8b1ceaa5e950a84b3b5fbf8228f25e277
https://git.kernel.org/stable/c/1586bd2d2fb436a26df20a70e78b000d34a7d159
https://git.kernel.org/stable/c/a3fd5dc1c7b0aae947a67dc2e2c037d57557a4de
https://git.kernel.org/stable/c/60d82592ac8b5637fbed871381eb0a16df0a492e
https://git.kernel.org/stable/c/dd9d3e16c2d5fa166e13dce07413be51f42c8f5d
reply other threads:[~2026-06-24 16:34 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=2026062444-CVE-2026-52992-af99@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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.