From nobody Mon Dec 1 23:35:11 2025 Received: from out30-99.freemail.mail.aliyun.com (out30-99.freemail.mail.aliyun.com [115.124.30.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 53A82219A86 for ; Wed, 26 Nov 2025 07:26:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=115.124.30.99 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764141993; cv=none; b=DA20uTD+yHavikj5Xy0Y4Shgci2AMoG/W8wXGOSHhtIaJwBoW3KyiKFjVIJnoxfZfeJCPh3o1Lg3ezZXH7gdpP3flFx+zNOXdrGmtRCnXWbXSFfBcvZhA1iBwo1bpLsXgDDYCRStesWVG0czV220JRXPrlCmsljTxJWTo+83V1w= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764141993; c=relaxed/simple; bh=6IWFSsnw4JQb2I/72pEIy41v0DsazfY5lvO4y25itq0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=GlZk/VfD+cqwC1rDPLrARBQ+apHWjrDJr4S3af6dsNre9GisWrd3e5R2SlG08jnLrdDkoafulR49F43jCvlNfx5OHIgaplye4cZTZt5ZBAZa/ZIPxqui9dR0evVqmMgLVU9EI1wj3Hm06QqknY7kh1HzUSHIBp6tIiISW3o8EfQ= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com; spf=pass smtp.mailfrom=linux.alibaba.com; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b=IrDedASf; arc=none smtp.client-ip=115.124.30.99 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b="IrDedASf" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.alibaba.com; s=default; t=1764141987; h=From:To:Subject:Date:Message-ID:MIME-Version; bh=C9a2f2XfJwa3R4E33CkXxML5twsuw6sq2btWRFT+oVk=; b=IrDedASfDVQO1JQ18I41xTmhMpbgyGpFOibhjJfiKHW0YLm0b27Aq+YqBQiUmBmgur2SgLqqdqnRDCbK9Gr/qfIB9Oh6gUdg5iNrzasUVC2C0qzG6zs9bRhOv8ZKDAJLHuEQApG6fwofLKHIKW5qNWcyoWU0GwYJbEGnTlSF4qY= Received: from localhost(mailfrom:kanie@linux.alibaba.com fp:SMTPD_---0WtREiL5_1764141983 cluster:ay36) by smtp.aliyun-inc.com; Wed, 26 Nov 2025 15:26:27 +0800 From: Guixin Liu To: Bjorn Helgaas , Andy Shevchenko Cc: linux-kernel@vger.kernel.org Subject: [PATCH v3] PCI: Check rom header and data structure addr before accessing Date: Wed, 26 Nov 2025 15:26:23 +0800 Message-ID: <20251126072623.62579-1-kanie@linux.alibaba.com> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" We meet a crash when running stress-ng on x86_64 machine: BUG: unable to handle page fault for address: ffa0000007f40000 RIP: 0010:pci_get_rom_size+0x52/0x220 Call Trace: pci_map_rom+0x80/0x130 pci_read_rom+0x4b/0xe0 kernfs_file_read_iter+0x96/0x180 vfs_read+0x1b1/0x300 Our analysis reveals that the rom space's start address is 0xffa0000007f30000, and size is 0x10000. Because of broken rom space, before calling readl(pds), the pds's value is 0xffa0000007f3ffff, which is already pointed to the rom space end, invoking readl() would read 4 bytes therefore cause an out-of-bounds access and trigger a crash. Fix this by adding image header and data structure checking. We also found another crash on arm64 machine: Unable to handle kernel paging request at virtual address ffff8000dd1393ff Mem abort info: ESR =3D 0x0000000096000021 EC =3D 0x25: DABT (current EL), IL =3D 32 bits SET =3D 0, FnV =3D 0 EA =3D 0, S1PTW =3D 0 FSC =3D 0x21: alignment fault The call trace is the same with x86_64, but the crash reason is that the data structure addr is not aligned with 4, and arm64 machine report "alignment fault". Fix this by adding alignment checking. Fixes: 47b975d234ea ("PCI: Avoid iterating through memory outside the resou= rce window") Suggested-by: Guanghui Feng Signed-off-by: Guixin Liu --- v2 -> v3: - Add pci_rom_header_valid() helper for checking image addr and signature. - Add pci_rom_data_struct_valid() helper for checking data struct add and signature. - Handle overflow issue when adding addr with size. - Handle alignment fault when running on arm64. v1 -> v2: - Fix commit body problems, such as blank line in "Call Trace" both sides, thanks, (Andy Shevchenko).=20 - Remove every step checking, just check the addr is in header or data stru= ct. - Add Suggested-by: Guanghui Feng tag. drivers/pci/rom.c | 86 +++++++++++++++++++++++++++++++++++++---------- 1 file changed, 69 insertions(+), 17 deletions(-) diff --git a/drivers/pci/rom.c b/drivers/pci/rom.c index e18d3a4383ba..8b4221d9fc17 100644 --- a/drivers/pci/rom.c +++ b/drivers/pci/rom.c @@ -69,6 +69,68 @@ void pci_disable_rom(struct pci_dev *pdev) } EXPORT_SYMBOL_GPL(pci_disable_rom); =20 +#define PCI_ROM_HEADER_SIZE 0x1A + +static inline bool pci_rom_header_valid(struct pci_dev *pdev, + void __iomem *image, + void __iomem *rom, + size_t size, + bool last_image) +{ + uintptr_t rom_end =3D (uintptr_t)rom + size; + uintptr_t header_end; + + if (check_add_overflow((uintptr_t)image, PCI_ROM_HEADER_SIZE, + &header_end)) + return false; + + if (image >=3D rom && header_end < rom_end && + IS_ALIGNED((uintptr_t)image, 2)) { + /* Standard PCI ROMs start out with these bytes 55 AA */ + if (readw(image) =3D=3D 0xAA55) + return true; + + if (!last_image) + pci_info(pdev, "No more image in the PCI ROM\n"); + else + pci_info(pdev, "Invalid PCI ROM header signature: expecting 0xaa55, got= %#06x\n", + readw(image)); + } + return false; +} + +static inline bool pci_rom_data_struct_valid(struct pci_dev *pdev, + void __iomem *pds, + void __iomem *rom, + size_t size) +{ + uintptr_t rom_end =3D (uintptr_t)rom + size; + uintptr_t end; + u16 data_len; + + if (!IS_ALIGNED((uintptr_t)pds, 4)) + return false; + + /* Before reading length, check range. */ + if (check_add_overflow((uintptr_t)pds, 0x0B, &end)) + return false; + + if (pds > rom && end < rom_end) { + data_len =3D readw(pds + 0x0A); + if (!data_len || data_len =3D=3D 0xFFFF || + check_add_overflow((uintptr_t)pds, data_len, &end)) + return false; + + if (end < rom_end) { + if (readl(pds) =3D=3D 0x52494350) + return true; + pci_info(pdev, "Invalid PCI ROM data signature: expecting 0x52494350, g= ot %#010x\n", + readl(pds)); + } + } + return false; +} + /** * pci_get_rom_size - obtain the actual size of the ROM image * @pdev: target PCI device @@ -90,31 +152,21 @@ static size_t pci_get_rom_size(struct pci_dev *pdev, v= oid __iomem *rom, image =3D rom; do { void __iomem *pds; - /* Standard PCI ROMs start out with these bytes 55 AA */ - if (readw(image) !=3D 0xAA55) { - pci_info(pdev, "Invalid PCI ROM header signature: expecting 0xaa55, got= %#06x\n", - readw(image)); + + if (!pci_rom_header_valid(pdev, image, rom, size, true)) break; - } + /* get the PCI data structure and check its "PCIR" signature */ pds =3D image + readw(image + 24); - if (readl(pds) !=3D 0x52494350) { - pci_info(pdev, "Invalid PCI ROM data signature: expecting 0x52494350, g= ot %#010x\n", - readl(pds)); + if (!pci_rom_data_struct_valid(pdev, pds, rom, size)) break; - } + last_image =3D readb(pds + 21) & 0x80; length =3D readw(pds + 16); image +=3D length * 512; - /* Avoid iterating through memory outside the resource window */ - if (image >=3D rom + size) + + if (!pci_rom_header_valid(pdev, image, rom, size, (bool)last_image)) break; - if (!last_image) { - if (readw(image) !=3D 0xAA55) { - pci_info(pdev, "No more image in the PCI ROM\n"); - break; - } - } } while (length && !last_image); =20 /* never return a size larger than the PCI resource window */ --=20 2.43.0