From: sashiko-bot@kernel.org
To: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/proc: Use file_ns_capable() when checking config space read access
Date: Mon, 20 Jul 2026 20:59:13 +0000 [thread overview]
Message-ID: <20260720205913.75B171F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260720204145.1500105-1-kwilczynski@kernel.org>
> proc_bus_pci_read() decides how much of the config space is readable
> based on capable(CAP_SYS_ADMIN), which checks the credentials of the
> task calling read(), not the credentials of the process that opened
> the file.
>
> The sysfs equivalent, pci_read_config(), has checked the credentials
> of the opening process since commit de139a339395 ("pci: check caps
> from sysfs file open to read device dependent config space"), so a
> privileged process can open the config space file and pass the file
> descriptor to an unprivileged process (for example, a process running
> a KVM guest with an assigned device), which can then read the entire
> config space. The check was subsequently routed through the LSM
> framework in commit 47970b1b2aa6 ("pci: use security_capable() when
> checking capablities during config space read") and converted to the
> dedicated helper in commit ab0fa82b2df9 ("pci-sysfs: use proper file
> [ ... ]
> As a result, a file descriptor opened by a privileged process and
> passed to an unprivileged one now allows the entire config space to
> be read through procfs, matching sysfs.
>
> Signed-off-by: Krzysztof Wilczyński <kwilczynski@kernel.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260720204145.1500105-1-kwilczynski@kernel.org?part=1
prev parent reply other threads:[~2026-07-20 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 20:41 [PATCH] PCI/proc: Use file_ns_capable() when checking config space read access Krzysztof Wilczyński
2026-07-20 20:59 ` sashiko-bot [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=20260720205913.75B171F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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