From: Chandradhar Kumar <chandradhar.2003@gmail.com>
To: song@kernel.org, yukuai@fygo.io, linux-raid@vger.kernel.org
Cc: magiclinan@didiglobal.com, xiao@kernel.org,
linux-kernel@vger.kernel.org,
Chandradhar Kumar <chandradhar.2003@gmail.com>,
syzbot+a32ff75e417c0f49a8e9@syzkaller.appspotmail.com
Subject: [PATCH v2] md/raid0: validate device count before allocating devlist
Date: Mon, 7 Sep 2026 00:14:06 +0530 [thread overview]
Message-ID: <20260906184406.2141-1-chandradhar.2003@gmail.com> (raw)
create_strip_zones() allocates conf->devlist based on mddev->raid_disks
before verifying that enough devices are present. Validate the number of
member devices before allocating devlist to reject invalid
configurations early.
The existing validation later in the function already rejects this
condition, but it occurs after the potentially excessive allocation.
Reported-by: syzbot+a32ff75e417c0f49a8e9@syzkaller.appspotmail.com
Closes: https://syzbot.org/bug?extid=a32ff75e417c0f49a8e9
Signed-off-by: Chandradhar Kumar <chandradhar.2003@gmail.com>
v2:
- Reject non-positive raid-disks values, which can bypass the device
count validation and result in an oversized allocation.
---
drivers/md/raid0.c | 20 +++++++++++++++++++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c
index 35e103f0c2c3..8eaf078606d6 100644
--- a/drivers/md/raid0.c
+++ b/drivers/md/raid0.c
@@ -69,7 +69,7 @@ static int create_strip_zones(struct mddev *mddev, struct r0conf **private_conf)
sector_t curr_zone_end, sectors;
struct md_rdev *smallest, *rdev1, *rdev2, *rdev, **dev;
struct strip_zone *zone;
- int cnt;
+ int cnt, nr_devs;
struct r0conf *conf = kzalloc_obj(*conf);
unsigned int blksize = 512;
@@ -79,7 +79,10 @@ static int create_strip_zones(struct mddev *mddev, struct r0conf **private_conf)
*private_conf = ERR_PTR(-ENOMEM);
if (!conf)
return -ENOMEM;
+
+ nr_devs = 0;
rdev_for_each(rdev1, mddev) {
+ nr_devs++;
pr_debug("md/raid0:%s: looking at %pg\n",
mdname(mddev),
rdev1->bdev);
@@ -144,6 +147,21 @@ static int create_strip_zones(struct mddev *mddev, struct r0conf **private_conf)
}
err = -ENOMEM;
+
+ if (mddev->raid_disks <= 0) {
+ pr_warn("md/raid0:%s: invalid number of disks %d - aborting!\n",
+ mdname(mddev), mddev->raid_disks);
+ err = -EINVAL;
+ goto abort;
+ }
+
+ if (nr_devs < mddev->raid_disks) {
+ pr_warn("md/raid0:%s: too few disks (%d of %d) - aborting!\n",
+ mdname(mddev), nr_devs, mddev->raid_disks);
+ err = -EINVAL;
+ goto abort;
+ }
+
conf->strip_zone = kvzalloc_objs(struct strip_zone, conf->nr_strip_zones);
if (!conf->strip_zone)
goto abort;
--
2.55.0
next reply other threads:[~2026-09-06 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 18:44 Chandradhar Kumar [this message]
2026-09-06 18:55 ` [PATCH v2] md/raid0: validate device count before allocating devlist sashiko-bot
2026-09-07 6:49 ` yu kuai
-- strict thread matches above, loose matches on Subject: below --
2026-09-06 14:39 [PATCH] " Chandradhar Kumar
2026-09-06 17:37 ` [PATCH v2] " 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=20260906184406.2141-1-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+a32ff75e417c0f49a8e9@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