From: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Christophe Leroy" <chleroy@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Kees Cook" <kees@kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI/sysfs: Fix out-of-bounds read in pci_write_legacy_io()
Date: Tue, 7 Jul 2026 03:05:45 +0900 [thread overview]
Message-ID: <20260706180158.GC265195@rocinante> (raw)
In-Reply-To: <20260616163131.2763281-1-kwilczynski@kernel.org>
Hello,
> pci_write_legacy_io() loads 4 bytes from the kernfs write buffer
> regardless of how many bytes userspace wrote:
>
> if (count != 1 && count != 2 && count != 4)
> return -EINVAL;
>
> return pci_legacy_write(bus, off, *(u32 *)buf, count);
>
> kernfs_fop_write_iter() allocates the buffer with kmalloc(len + 1),
> so a 1-byte write to the legacy_io sysfs file allocates 2 bytes and
> the unconditional u32 load reads up to 2 bytes past the end of the
> allocation, which KASAN reports as a slab-out-of-bounds read.
> Similarly, a 2-byte write overreads by 1 byte.
>
> Thus, read only the number of bytes requested using get_unaligned_le16()
> and get_unaligned_le32() for the 2 and 4 byte cases, interpreting the
> buffer as little-endian to match the byte ordering of PCI I/O port
> space.
>
> The PowerPC implementation previously compensated for the generic
> code's native-endian 32-bit load by shifting the value into place
> for the 1 and 2 byte cases. The shifts were only correct on
> big-endian kernels.
>
> On little-endian PowerPC (POWER8 and later), they extracted the wrong
> bytes, so a 1-byte write wrote an out-of-bounds byte instead of the
> requested value. On big-endian, the native load also caused out_le16()
> and out_le32() to reverse the user's bytes on the wire for 2 and 4 byte
> writes. The little-endian helpers resolve both issues, so the shifts
> are removed.
>
> No changes are needed for the Alpha platform.
>
> The legacy_io file is root-only and exists only on Alpha and PowerPC,
> the two architectures that define HAVE_PCI_LEGACY.
Applied to the sysfs branch. I would like for the 0-day bot to pick this
up, and also to have some linux-next soak time, if possible.
Thank you!
Krzysztof
prev parent reply other threads:[~2026-07-06 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 16:31 [PATCH 1/2] PCI/sysfs: Fix out-of-bounds read in pci_write_legacy_io() Krzysztof Wilczyński
2026-06-16 16:31 ` [PATCH 2/2] PCI/sysfs: Fix read byte order in pci_read_legacy_io() Krzysztof Wilczyński
2026-06-16 16:36 ` sashiko-bot
2026-06-16 16:42 ` [PATCH 1/2] PCI/sysfs: Fix out-of-bounds read in pci_write_legacy_io() sashiko-bot
2026-06-16 16:47 ` Krzysztof Wilczyński
2026-07-06 18:05 ` Krzysztof Wilczyński [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=20260706180158.GC265195@rocinante \
--to=kwilczynski@kernel.org \
--cc=bhelgaas@google.com \
--cc=chleroy@kernel.org \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.