From: Chandradhar Kumar <chandradhar.2003@gmail.com>
To: song@kernel.org, yukuai@fygo.io
Cc: xiao@kernel.org, magiclinan@didiglobal.com,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+9e3014263a35700ab49b@syzkaller.appspotmail.com,
Chandradhar Kumar <chandradhar.2003@gmail.com>
Subject: [PATCH v5 1/3] md: validate v0.90 superblock disk bounds on load and sync
Date: Tue, 17 Nov 2026 14:50:51 +0530 [thread overview]
Message-ID: <20261117092053.10884-2-chandradhar.2003@gmail.com> (raw)
In-Reply-To: <20261117092053.10884-1-chandradhar.2003@gmail.com>
The legacy v0.90 superblock format (mdp_super_t) only holds MD_SB_DISKS
(27) disk descriptors in sb->disks[]. Unvalidated disk indices or an
out-of-range desc_nr can cause super_90_sync() to index past the end of
sb->disks[]:
UBSAN: array-index-out-of-bounds in drivers/md/md.c:1740:29
index 124 is out of range for type 'mdp_disk_t [27]'
Harden on-disk v0.90 metadata loading, validation, and superblock
synchronization against out-of-bounds indices:
1. In super_90_load(), reject superblocks where sb->this_disk.number >=
MD_SB_DISKS, where a v0.91+ reshape has a pre-reshape disk count
outside [1, MD_SB_DISKS], or where an active/sync descriptor has
raid_disk >= MD_SB_DISKS.
2. In super_90_validate(), check rdev->desc_nr at the start of the
function before any sb->disks[] dereference, and verify
desc->raid_disk < MD_SB_DISKS before assigning rdev->raid_disk.
3. In super_90_sync(), bounds-check desc_nr and mddev->raid_disks
before indexing sb->disks[]. If rdev->desc_nr is out of range (such
as an excess spare or failed slot on a full 27-disk array),
synthesize a faulty/removed this_disk descriptor with rdev->desc_nr
rather than indexing out-of-bounds or zeroing this_disk (which would
alias active slot 0 on subsequent assembly).
Fixes: 1a33a379e678 ("md: reject v0.90 arrays with too many devices")
Reported-by: syzbot+9e3014263a35700ab49b@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=9e3014263a35700ab49b
Signed-off-by: Chandradhar Kumar <chandradhar.2003@gmail.com>
---
drivers/md/md.c | 40 +++++++++++++++++++++++++++++++++++++---
1 file changed, 37 insertions(+), 3 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 03e35386a802..6baf209703c8 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -1407,7 +1407,18 @@ static int super_90_load(struct md_rdev *rdev, struct md_rdev *refdev, int minor
goto abort;
}
- if (sb->raid_disks <= 0 || sb->raid_disks > MD_SB_DISKS)
+ if (sb->raid_disks <= 0 || sb->raid_disks > MD_SB_DISKS ||
+ sb->this_disk.number >= MD_SB_DISKS)
+ goto abort;
+
+ if (sb->minor_version >= 91 &&
+ ((s64)sb->raid_disks - (s32)sb->delta_disks <= 0 ||
+ (s64)sb->raid_disks - (s32)sb->delta_disks > MD_SB_DISKS))
+ goto abort;
+
+ if ((sb->disks[sb->this_disk.number].state &
+ ((1 << MD_DISK_SYNC) | (1 << MD_DISK_ACTIVE))) &&
+ sb->disks[sb->this_disk.number].raid_disk >= MD_SB_DISKS)
goto abort;
if (md_csum_fold(calc_sb_csum(sb)) != md_csum_fold(sb->sb_csum)) {
@@ -1501,6 +1512,9 @@ static int super_90_validate(struct mddev *mddev, struct md_rdev *freshest, stru
clear_bit(Bitmap_sync, &rdev->flags);
clear_bit(WriteMostly, &rdev->flags);
+ if (rdev->desc_nr < 0 || rdev->desc_nr >= MD_SB_DISKS)
+ return -EINVAL;
+
if (mddev->raid_disks == 0) {
mddev->major_version = 0;
mddev->minor_version = sb->minor_version;
@@ -1592,6 +1606,8 @@ static int super_90_validate(struct mddev *mddev, struct md_rdev *freshest, stru
if (desc->state & (1<<MD_DISK_FAULTY))
set_bit(Faulty, &rdev->flags);
else if (desc->state & (1<<MD_DISK_SYNC)) {
+ if (desc->raid_disk >= MD_SB_DISKS)
+ return -EINVAL;
set_bit(In_sync, &rdev->flags);
rdev->raid_disk = desc->raid_disk;
rdev->saved_raid_disk = desc->raid_disk;
@@ -1601,6 +1617,8 @@ static int super_90_validate(struct mddev *mddev, struct md_rdev *freshest, stru
* that is, so set to zero for now
*/
if (mddev->minor_version >= 91) {
+ if (desc->raid_disk >= MD_SB_DISKS)
+ return -EINVAL;
rdev->recovery_offset = 0;
rdev->raid_disk = desc->raid_disk;
}
@@ -1708,6 +1726,12 @@ static void super_90_sync(struct mddev *mddev, struct md_rdev *rdev)
else
desc_nr = next_spare++;
rdev2->desc_nr = desc_nr;
+
+ if (desc_nr < 0 || desc_nr >= MD_SB_DISKS) {
+ pr_warn("md: %s: desc_nr %d out of range for rdev %pg, skipping\n",
+ mdname(mddev), desc_nr, rdev2->bdev);
+ continue;
+ }
d = &sb->disks[rdev2->desc_nr];
nr_disks++;
d->number = rdev2->desc_nr;
@@ -1736,7 +1760,7 @@ static void super_90_sync(struct mddev *mddev, struct md_rdev *rdev)
d->state |= (1<<MD_DISK_FAILFAST);
}
/* now set the "removed" and "faulty" bits on any missing devices */
- for (i=0 ; i < mddev->raid_disks ; i++) {
+ for (i = 0 ; i < mddev->raid_disks && i < MD_SB_DISKS; i++) {
mdp_disk_t *d = &sb->disks[i];
if (d->state == 0 && d->number == 0) {
d->number = i;
@@ -1752,7 +1776,17 @@ static void super_90_sync(struct mddev *mddev, struct md_rdev *rdev)
sb->failed_disks = failed;
sb->spare_disks = spare;
- sb->this_disk = sb->disks[rdev->desc_nr];
+ if (rdev->desc_nr >= 0 && rdev->desc_nr < MD_SB_DISKS) {
+ sb->this_disk = sb->disks[rdev->desc_nr];
+ } else {
+ sb->this_disk.number = rdev->desc_nr;
+ sb->this_disk.major = MAJOR(rdev->bdev->bd_dev);
+ sb->this_disk.minor = MINOR(rdev->bdev->bd_dev);
+ sb->this_disk.raid_disk = rdev->desc_nr;
+ sb->this_disk.state = (1 << MD_DISK_FAULTY) |
+ (1 << MD_DISK_REMOVED);
+ }
+
sb->sb_csum = calc_sb_csum(sb);
}
--
2.56.1
next prev parent reply other threads:[~2026-11-17 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 9:20 [PATCH v5 0/3] md: enforce MD_SB_DISKS bounds across v0.90 superblock paths Chandradhar Kumar
2026-11-17 9:20 ` Chandradhar Kumar [this message]
2026-11-17 9:20 ` [PATCH v5 2/3] md: maintain max_disks for v0.90 arrays in metadata_store and ioctl Chandradhar Kumar
2026-11-17 9:20 ` [PATCH v5 3/3] md: enforce max_disks and MD_SB_DISKS in raid_disks and slot sysfs stores Chandradhar Kumar
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=20261117092053.10884-2-chandradhar.2003@gmail.com \
--to=chandradhar.2003@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=song@kernel.org \
--cc=syzbot+9e3014263a35700ab49b@syzkaller.appspotmail.com \
--cc=xiao@kernel.org \
--cc=yukuai@fygo.io \
/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
all inboxes | Powered by JetHome®