From: Andreas Larsson <andreas@gaisler.com>
To: Miaoqian Lin <linmq006@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Lars Kotthoff <metalhead@metalhead.ws>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] sparc/led: prevent buffer underflow on zero-length write
Date: Wed, 14 Jan 2026 09:40:28 +0100 [thread overview]
Message-ID: <ea889379-7cc9-4e03-8040-2797acfb375c@gaisler.com> (raw)
In-Reply-To: <20251030072156.30656-1-linmq006@gmail.com>
On 2025-10-30 08:21, Miaoqian Lin wrote:
> Fix out-of-bounds access in led_proc_write() when count is 0.
> Accessing buf[count - 1] with count=0 reads/writes buf[-1].
>
> Check for count==0 and return -EINVAL early to fix this.
>
> Found via static analysis and code review.
>
> Fixes: ee1858d3122d ("[SPARC]: Add sun4m LED driver.")
> Cc: stable@vger.kernel.org
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
> ---
> arch/sparc/kernel/led.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/sparc/kernel/led.c b/arch/sparc/kernel/led.c
> index f4fb82b019bb..aa0ca0d8d0e2 100644
> --- a/arch/sparc/kernel/led.c
> +++ b/arch/sparc/kernel/led.c
> @@ -70,6 +70,9 @@ static ssize_t led_proc_write(struct file *file, const char __user *buffer,
> {
> char *buf = NULL;
>
> + if (count == 0)
> + return -EINVAL;
> +
> if (count > LED_MAX_LENGTH)
> count = LED_MAX_LENGTH;
>
Thank you for the patch.
I see no need to fail on the empty string in particular when further
down we have a default case:
} else {
auxio_set_led(AUXIO_LED_OFF);
}
for any string not matching particular cases.
Instead, please stop the incorrect buffer access with something like:
diff --git a/arch/sparc/kernel/led.c b/arch/sparc/kernel/led.c
index f4fb82b019bb9..9b53ac1fe533d 100644
--- a/arch/sparc/kernel/led.c
+++ b/arch/sparc/kernel/led.c
@@ -78,7 +78,7 @@ static ssize_t led_proc_write(struct file *file, const char __user *buffer,
return PTR_ERR(buf);
/* work around \n when echo'ing into proc */
- if (buf[count - 1] == '\n')
+ if (count > 0 && buf[count - 1] == '\n')
buf[count - 1] = '\0';
/* before we change anything we want to stop any running timers,
Thanks,
Andreas
prev parent reply other threads:[~2026-01-14 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 7:21 Miaoqian Lin
2026-01-14 8:40 ` Andreas Larsson [this message]
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=ea889379-7cc9-4e03-8040-2797acfb375c@gaisler.com \
--to=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=metalhead@metalhead.ws \
--cc=mingo@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®