From: Greg KH <gregkh@linuxfoundation.org>
To: Saifuddin Kaijar <mailtokaijar@gmail.com>
Cc: security@kernel.org, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [SECURITY] Samsung Exynos SROM: Out-of-bounds write via unchecked device tree bank parameter
Date: Fri, 24 Apr 2026 06:01:26 +0200 [thread overview]
Message-ID: <2026042436-unnoticed-barracuda-56e4@gregkh> (raw)
In-Reply-To: <CAD7tK9b8VFPan6tMmOv+_juaYc1Ycfy6t4DoioKDeLGE7ECqeg@mail.gmail.com>
On Fri, Apr 24, 2026 at 04:40:47AM +0530, Saifuddin Kaijar wrote:
> Dear Linux Kernel Security Team,
>
> I am reporting a security vulnerability in the Samsung Exynos SROM driver.
>
> SUMMARY:
> Out-of-bounds MMIO write due to missing validation of device tree bank
> parameter.
>
> COMPONENT:
> File: drivers/memory/samsung/exynos-srom.c
> Function: exynos_srom_configure_bank()
> Lines: 74-100
>
> AFFECTED VERSIONS:
> All kernels since 3.15 (2015) up to current mainline (6.12.1)
>
> SEVERITY:
> HIGH (CVSS 7.8: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
> CWE-787: Out-of-bounds Write
>
> DESCRIPTION:
> The driver reads 'bank' parameter from device tree without validation,
> then uses it as an offset for MMIO register writes:
device tree is trusted, so this isn't a valid security issue, or
probably even a bug at all, sorry.
If you wish to fix this, please just send a patch to the developer and
mailing list.
thanks,
greg k-h
next parent reply other threads:[~2026-04-24 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAD7tK9b8VFPan6tMmOv+_juaYc1Ycfy6t4DoioKDeLGE7ECqeg@mail.gmail.com>
2026-04-24 4:01 ` Greg KH [this message]
2026-04-23 23:17 [SECURITY] Samsung Exynos SROM: Out-of-bounds write via unchecked device tree bank parameter Saifuddin Kaijar
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=2026042436-unnoticed-barracuda-56e4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mailtokaijar@gmail.com \
--cc=security@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox