From: Raag Jadav <raag.jadav@intel.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Reuven Abliyev <reuven.abliyev@intel.com>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Jani Partanen <jiipee@sotapeli.fi>,
Lucas De Marchi <demarchi@kernel.org>
Subject: Re: [PATCH] mtd: intel-dg: Fix accessing regions before setting nregions
Date: Thu, 15 Jan 2026 06:58:51 +0100 [thread overview]
Message-ID: <aWiCG7LyGMhmfsjZ@black.igk.intel.com> (raw)
In-Reply-To: <20260115052237.1149027-1-alexander.usyskin@intel.com>
On Thu, Jan 15, 2026 at 07:22:37AM +0200, Alexander Usyskin wrote:
> The regions array is counted by nregions, but it's set only after
> accessing it:
>
> [] UBSAN: array-index-out-of-bounds in drivers/mtd/devices/mtd_intel_dg.c:750:15
> [] index 0 is out of range for type '<unknown> [*]'
>
> Fix it by also fixing an undesired behavior: the loop silently ignores
> ENOMEM and continues setting the other entries.
>
> CC: Gustavo A. R. Silva <gustavoars@kernel.org>
> CC: Raag Jadav <raag.jadav@intel.com>
> Reported-by: Jani Partanen <jiipee@sotapeli.fi>
> Closes: https://lore.kernel.org/all/caca6c67-4f1d-49f1-948f-e63b6b937b29@sotapeli.fi
> Fixes: ceb5ab3cb646 ("mtd: add driver for intel graphics non-volatile memory device")
> Signed-off-by: Lucas De Marchi <demarchi@kernel.org>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/mtd/devices/mtd_intel_dg.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mtd/devices/mtd_intel_dg.c b/drivers/mtd/devices/mtd_intel_dg.c
> index 2bab30dcd35f..7f751c48a76d 100644
> --- a/drivers/mtd/devices/mtd_intel_dg.c
> +++ b/drivers/mtd/devices/mtd_intel_dg.c
> @@ -770,6 +770,7 @@ static int intel_dg_mtd_probe(struct auxiliary_device *aux_dev,
>
> kref_init(&nvm->refcnt);
> mutex_init(&nvm->lock);
> + nvm->nregions = nregions;
>
> for (n = 0, i = 0; i < INTEL_DG_NVM_REGIONS; i++) {
> if (!invm->regions[i].name)
> @@ -777,13 +778,15 @@ static int intel_dg_mtd_probe(struct auxiliary_device *aux_dev,
>
> char *name = kasprintf(GFP_KERNEL, "%s.%s",
> dev_name(&aux_dev->dev), invm->regions[i].name);
> - if (!name)
> - continue;
> + if (!name) {
> + ret = -ENOMEM;
> + goto err;
> + }
> +
> nvm->regions[n].name = name;
> nvm->regions[n].id = i;
> n++;
> }
> - nvm->nregions = n; /* in case where kasprintf fail */
>
> ret = devm_pm_runtime_enable(device);
> if (ret < 0) {
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-01-15 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 5:22 [PATCH] mtd: intel-dg: Fix accessing regions before setting nregions Alexander Usyskin
2026-01-15 5:58 ` Raag Jadav [this message]
2026-01-19 10:49 ` Miquel Raynal
-- strict thread matches above, loose matches on Subject: below --
2025-11-11 15:28 Lucas De Marchi
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=aWiCG7LyGMhmfsjZ@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=demarchi@kernel.org \
--cc=gustavoars@kernel.org \
--cc=jiipee@sotapeli.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=reuven.abliyev@intel.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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