From: Guenter Roeck <linux@roeck-us.net>
To: Ninad Malwade <nmalwade@nvidia.com>
Cc: treding@nvidia.com, jonathanh@nvidia.com, jdelvare@suse.com,
nicolinc@nvidia.com, rkasirajan@nvidia.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] hwmon: (ina3221): tighten attribute sysfs permissions
Date: Thu, 17 Nov 2022 06:27:14 -0800 [thread overview]
Message-ID: <20221117142714.GB664755@roeck-us.net> (raw)
In-Reply-To: <20221117083920.20493-1-nmalwade@nvidia.com>
On Thu, Nov 17, 2022 at 04:39:20PM +0800, Ninad Malwade wrote:
> The INA3221 device provides voltage and current measurements for
> various power rails, including the CPU rail, on at least some Jetson
> boards. This raises the possibility of the Platypus attack being relevant
> to Jetson. To prevent this possibility, modify all attribute
> channel permissions so that only root can access the values.
NACK. The hwmon ABI expects all attributes to be readable for everyone.
Forcing userspace to have root privilege to read sensor values just moves
the attack vector into the affected applications.
You have a number of options:
1) Make the values reported vague enough to be useless for attacks
2) Remove the attributes
3) Remove the driver
2) and 3) are obviously unacceptable here. Your option would be to
disable the driver on the affected system.
Having said that, for me to accept any driver change, you would have to
prove that the values reported by the chip are really accurate enough to
be useful in any attack (most chips do not deliver that level of accuracy).
A generic statement along the line of "raises the possibility" is
insufficient.
> This is logically equivalent to 949dd0104c49 ("powercap: restrict energy
> meter to root access") upstream.
The change in the powercap driver is not hwmon ABI related and
irrelevant. If you look for an example, use commit 9049572fb145
("hwmon: Remove amd_energy driver").
Guenter
prev parent reply other threads:[~2022-11-17 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 8:39 Ninad Malwade
2022-11-17 14:27 ` Guenter Roeck [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=20221117142714.GB664755@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=jonathanh@nvidia.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=nmalwade@nvidia.com \
--cc=rkasirajan@nvidia.com \
--cc=treding@nvidia.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®