From nobody Sat Jul 25 02:35:47 2026 Received: from dggsgout11.his.huawei.com (dggsgout11.his.huawei.com [45.249.212.51]) (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 ABDB640DFDE; Mon, 20 Jul 2026 13:26:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.51 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784553986; cv=none; b=eS4cXn6PriVTS4qO+AN5SmXHuZhgVRCEJVOxj+ylViQNMITlBNI/eIyyGBg1jwgr8HsfJ+IlDc3IKzdmmoTa/7nd/ELqpPJP+F2CH6ooH56kVoVre/C+lKCIoHvuOvjxOREuNxBVhIDZU8n7IekgCczAd6RlGKqmwh9or6PvhpM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784553986; c=relaxed/simple; bh=ZGawmCXaYx/QVK3hYcXSBEwi4LPgFTI3S+rYbVPvmvo=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=qdaGLrrfHTXziG/IONVCFIDD0vUynwLcHOHlOY43nmFXAVmH32j6zU5+hTrEtyXl1LpkySLjNkyLGCSH8DBdwRp8nZhs7wRs8fzaFeJE9h1DumjbE1tNHuC1rv0DhyPJasH6y2epz4pU1ec9b4oNHtTOJ4hkjgWuK5OMNxQOsFI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=huaweicloud.com; spf=pass smtp.mailfrom=huaweicloud.com; arc=none smtp.client-ip=45.249.212.51 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=huaweicloud.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huaweicloud.com Received: from mail.maildlp.com (unknown [172.19.163.177]) by dggsgout11.his.huawei.com (SkyGuard) with ESMTPS id 4h3h9G4QQfzYQtp4; Mon, 20 Jul 2026 21:25:54 +0800 (CST) Received: from mail02.huawei.com (unknown [10.116.40.112]) by mail.maildlp.com (Postfix) with ESMTP id 450534058C; Mon, 20 Jul 2026 21:26:20 +0800 (CST) Received: from ultra.huawei.com (unknown [10.90.53.71]) by APP1 (Coremail) with UTF8SMTPA id cCh0CgAHGHT6IV5qBcGqBw--.35011S2; Mon, 20 Jul 2026 21:26:20 +0800 (CST) From: Pu Lehui To: Tony Nguyen , Przemek Kitszel , Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Jeff Garzik , Auke Kok , Breno Leitao Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org, Pu Lehui , Pu Lehui Subject: [PATCH net v2] e1000e: Fix out-of-bounds MMIO access by validating BAR0 size Date: Mon, 20 Jul 2026 13:30:49 +0000 Message-Id: <20260720133049.1289167-1-pulehui@huaweicloud.com> X-Mailer: git-send-email 2.34.1 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 X-CM-TRANSID: cCh0CgAHGHT6IV5qBcGqBw--.35011S2 X-Coremail-Antispam: 1UD129KBjvJXoWxWFyUtr1rZFWrGF4rKrWUXFb_yoWrZr4kpa y3Ga47ur4rJr17X3W8Jr4UWFZ8Cayjyay5Cry2gwsY9FyUKry8Jry7tFW3Gr4xZFWktF9x tryUZ34Ikr4qyaUanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU9F14x267AKxVW8JVW5JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26r1j6r1xM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26F4j 6r4UJwA2z4x0Y4vEx4A2jsIE14v26F4UJVW0owA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Gc CE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0E 2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJV W8JwACjcxG0xvY0x0EwIxGrwACjI8F5VA0II8E6IAqYI8I648v4I1lFIxGxcIEc7CjxVA2 Y2ka0xkIwI1lc7CjxVAaw2AFwI0_Jw0_GFyl42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x 0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGVWUWwC2 zVAF1VAY17CE14v26r1q6r43MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF 4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r4j6F4UMIIF0xvE42xK8VAvwI8IcIk0rVWUJVWU CwCI42IY6I8E87Iv67AKxVW8JVWxJwCI42IY6I8E87Iv6xkF7I0E14v26r4UJVWxJrUvcS sGvfC2KfnxnUUI43ZEXa7VUbGQ6JUUUUU== X-CM-SenderInfo: psxovxtxl6x35dzhxuhorxvhhfrp/ Content-Type: text/plain; charset="utf-8" From: Pu Lehui Syzkaller reported a kernel panic caused by an out-of-bounds MMIO access in the e1000e driver. [ 82.868719][ T404] e1000e 0000:00:02.0: The NVM Checksum Is Not Valid [ 82.872328][ T404] Unable to handle kernel paging request at virtual ad= dress ffff80008894e090 [ 83.085218][ T404] CPU: 2 UID: 0 PID: 404 Comm: bash Not tainted 7.2.0-= rc2-g3f1f75536668 #1 PREEMPTLAZY [ 83.129013][ T404] pc : e1000_get_cfg_done_82571+0x70/0x158 [ 83.140092][ T404] lr : e1000_get_cfg_done_82571+0x68/0x158 [ 83.151196][ T404] sp : ffff80008ac37410 [ 83.158922][ T404] x29: ffff80008ac37410 x28: ffff0000cd6a11b8 x27: fff= f0000c58190d0 [ 83.173919][ T404] x26: ffff0000cd6a11b8 x25: ffff0000cd6a0bc0 x24: fff= f0000cd6a0000 [ 83.189417][ T404] x23: 0000000000001010 x22: ffff0000cd6a11c0 x21: fff= f0000cd6a11b8 [ 83.205195][ T404] x20: 0000000000000064 x19: ffff80008894e090 x18: 000= 0000000000000 [ 83.220545][ T404] x17: ffff800081c1a3f4 x16: ffff800081c19c10 x15: fff= f800081e86510 [ 83.235764][ T404] x14: 0000000000000001 x13: 0000000000000001 x12: fff= f60001bc8a8b3 [ 83.251301][ T404] x11: 1fffe0001bc8a8b2 x10: ffff60001bc8a8b2 x9 : fff= f800081eae25c [ 83.266705][ T404] x8 : 00009fffe437574e x7 : ffff0000de454593 x6 : 000= 0000000000001 [ 83.281919][ T404] x5 : ffff0000cf2b9640 x4 : 0000000000000000 x3 : dff= f800000000000 [ 83.297317][ T404] x2 : 0000000000000007 x1 : ffff0000cd6a11c0 x0 : 000= 0000000000000 [ 83.312601][ T404] Call trace: [ 83.318662][ T404] e1000_get_cfg_done_82571+0x70/0x158 (P) [ 83.329748][ T404] e1000e_phy_hw_reset_generic+0x17c/0x1a8 [ 83.341541][ T404] e1000_probe+0xbd8/0x1988 [ 83.350334][ T404] local_pci_probe+0x84/0x130 Repetition steps: 1. Find PCI device which BAR0 size <=3D 4K. If it's: Device Addr: 0000:00:02.0 BAR0 SIZE: 4K Vendor/Device ID: 0x1af4 0x1004 2. Unbind the above PCI device echo '0000:00:02.0' > /sys/bus/pci/devices/0000:00:02.0/driver/unbind 3. Set the above device to e1000e new_id echo '1af4 1004' > /sys/bus/pci/drivers/e1000e/new_id During e1000_probe(), the driver maps the device's BAR0 memory region. If the device has a 4K BAR0, ioremap() maps only 4K of space. Later in the probe process, when the NVM checksum validation fails, the driver attempts to perform a hardware reset and falls back to the err_eeprom cleanup path. This cleanup path will trigger an OOB access kernel panic: e1000_phy_hw_reset e1000e_phy_hw_reset_generic e1000_get_cfg_done_82571 er32(EEMNGCTL) readl(hw->hw_addr + EEMNGCTL); <-- EEMNGCTL(0x1010) > 4K, OOB access Fix this by ensuring the MMIO length (pci_resource_len(pdev, 0)) is at least 64K (0x10000) before proceeding with ioremap(). The 64K minimum safely covers the maximum register offset accessed by the e1000e driver. Fixes: bc7f75fa9788 ("[E1000E]: New pci-express e1000 driver (currently for= ICH9 devices only)") Signed-off-by: Pu Lehui --- v2: - Update comment about E1000_MMIO_LEN_MIN. (Breno) drivers/net/ethernet/intel/e1000e/netdev.c | 5 +++++ drivers/net/ethernet/intel/e1000e/regs.h | 3 +++ 2 files changed, 8 insertions(+) diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c b/drivers/net/ether= net/intel/e1000e/netdev.c index 844f31ab37ad..46e58e926f7b 100644 --- a/drivers/net/ethernet/intel/e1000e/netdev.c +++ b/drivers/net/ethernet/intel/e1000e/netdev.c @@ -7450,6 +7450,11 @@ static int e1000_probe(struct pci_dev *pdev, const s= truct pci_device_id *ent) mmio_len =3D pci_resource_len(pdev, 0); =20 err =3D -EIO; + if (mmio_len < E1000_MMIO_LEN_MIN) { + dev_err(&pdev->dev, "MMIO len is too small\n"); + goto err_ioremap; + } + adapter->hw.hw_addr =3D ioremap(mmio_start, mmio_len); if (!adapter->hw.hw_addr) goto err_ioremap; diff --git a/drivers/net/ethernet/intel/e1000e/regs.h b/drivers/net/etherne= t/intel/e1000e/regs.h index 6c0cd8cab3ef..dbabd35f5a12 100644 --- a/drivers/net/ethernet/intel/e1000e/regs.h +++ b/drivers/net/ethernet/intel/e1000e/regs.h @@ -242,4 +242,7 @@ /* PHY registers */ #define I82579_DFT_CTRL PHY_REG(769, 20) =20 +/* Smallest BAR0 that covers every register the driver accesses */ +#define E1000_MMIO_LEN_MIN 0x10000 + #endif --=20 2.34.1