mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Sanman Pradhan <psanman@juniper.net>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Pradhan, Sanman" <sanman.pradhan@hpe.com>
Subject: Re: [PATCH] hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read
Date: Wed, 4 Mar 2026 07:30:21 +0200	[thread overview]
Message-ID: <aafDbdT3lptQyt2_@ashevche-desk.local> (raw)
In-Reply-To: <SA1PR05MB8708FB8CDA1A57DE77D158A7BA7CA@SA1PR05MB8708.namprd05.prod.outlook.com>

On Wed, Mar 04, 2026 at 01:00:55AM +0000, Sanman Pradhan wrote:
> From 166d8a9220dc783b752cb212937a31e6e1adc811 Mon Sep 17 00:00:00 2001
> From: Sanman Pradhan <psanman@juniper.net>
> Date: Tue, 3 Mar 2026 16:22:08 -0800
> Subject: [PATCH] hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read

Something went wrong with your email.

Code wise the change LGTM.

> The q54sj108a2_debugfs_read function suffers from a stack buffer overflow
> due to incorrect arguments passed to bin2hex(). The function currently
> passes 'data' as the destination and 'data_char' as the source.
> 
> Because bin2hex() converts each input byte into two hex characters, a
> 32-byte block read results in 64 bytes of output. Since 'data' is only
> 34 bytes (I2C_SMBUS_BLOCK_MAX + 2), this writes 30 bytes past the end
> of the buffer onto the stack.
> 
> Additionally, the arguments were swapped: it was reading from the
> zero-initialized 'data_char' and writing to 'data', resulting in
> all-zero output regardless of the actual I2C read.
> 
> Fix this by:
> 1. Expanding 'data_char' to 66 bytes to safely hold the hex output.
> 2. Correcting the bin2hex() argument order and using the actual read count.
> 3. Using a pointer to select the correct output buffer for the final
>    simple_read_from_buffer call.

...

> -- 
> 2.34.1
> 
> 
> Thank you.
> 
> Regards,
> Sanman Pradhan

Ah, you copied and pasted the real email into another one. No, please use
proper tooling, exempli gratia `git send-email`.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-03-04  5:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  1:00 Sanman Pradhan
2026-03-04  5:30 ` Andy Shevchenko [this message]
2026-03-04  5:39 ` Guenter Roeck
2026-03-04  7:06 ` [PATCH v2] " Sanman Pradhan
2026-03-04 22:05   ` Guenter Roeck
2026-03-04 23:51     ` [PATCH v3] " Sanman Pradhan
2026-03-05  0:48       ` Guenter Roeck
2026-03-05 14:45       ` Guenter Roeck

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=aafDbdT3lptQyt2_@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=psanman@juniper.net \
    --cc=rdunlap@infradead.org \
    --cc=sanman.pradhan@hpe.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

all inboxes | Powered by JetHome®