HID: amd_sfh: Validate PCI BAR size before mapping

Description

In the Linux kernel, the following vulnerability has been resolved: HID: amd_sfh: Validate PCI BAR size before mapping The amd_sfh driver maps PCI BAR 2 using pcim_iomap_regions() and subsequently accesses MMIO registers at offsets up to 0x10958 (e.g., AMD_P2C_MSG3 at 0x1068C). However, the driver never validates that the BAR size is large enough to cover these accesses. If the driver is bound to a device with a smaller BAR 2, this leads to an out-of-bounds memory access and a page fault during the probe function. For example, a page fault can occur when reading from privdata->mmio + AMD_P2C_MSG3 in mp2_select_ops(): BUG: unable to handle page fault for address: ffffc9000390368c PGD 100000067 P4D 100000067 PUD 1012c1067 PMD 105b64067 PTE 0 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:readl arch/x86/include/asm/io.h:59 [inline] RIP: 0010:mp2_select_ops drivers/hid/amd-sfh-hid/amd_sfh_pcie.c:282 [inline] RIP: 0010:amd_mp2_pci_probe+0x337/0x5f0 drivers/hid/amd-sfh-hid/amd_sfh_pcie.c:487 Call Trace: <TASK> local_pci_probe drivers/pci/pci-driver.c:332 [inline] pci_call_probe drivers/pci/pci-driver.c:394 [inline] __pci_device_probe drivers/pci/pci-driver.c:455 [inline] pci_device_probe+0x431/0xc90 drivers/pci/pci-driver.c:489 Fix this by verifying that the length of BAR 2 is at least 128KB before attempting to map it. Since the maximum accessed offset is 0x10958, and PCI BAR sizes are powers of 2, any legitimate hardware will have a BAR size of at least 128KB.

Timeline

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)

0.21% · top 89% of all CVEs (12 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

• Linux · Linux

  • affected 4f567b9f8141a86c7d878fadf136e5d1408e3e61 – < 92bf2883da0306ab9d1eb794acd1058fc5088ebc
  • affected 4f567b9f8141a86c7d878fadf136e5d1408e3e61 – < 7b3747d77767f066ccf4a9e8e3a8381643ab5368
  • affected 4f567b9f8141a86c7d878fadf136e5d1408e3e61 – < 5ff24aa7af0bca0780fe4e6effce902065f2c0a7
  • affected 4f567b9f8141a86c7d878fadf136e5d1408e3e61 – < dc687489131559ee52f447592f6d039a5a013061
  • affected 4f567b9f8141a86c7d878fadf136e5d1408e3e61 – < 5f9e2ecb725adced013fbf5f94b9f185fad2e7d9
  • affected 4f567b9f8141a86c7d878fadf136e5d1408e3e61 – < ee25833f037fa22d23ffdbfeebabe3579e8a0346
  • affected 4f567b9f8141a86c7d878fadf136e5d1408e3e61 – < 65bcc5f89704efe5b9d69d4ea2c1002d90c31382

• Linux · Linux

  • affected 5.11
  • unaffected < 5.11
  • unaffected 5.15.222 – ≤ 5.15.*
  • unaffected 6.1.189 – ≤ 6.1.*
  • unaffected 6.6.158 – ≤ 6.6.*
  • unaffected 6.12.112 – ≤ 6.12.*
  • unaffected 6.18.55 – ≤ 6.18.*
  • unaffected 7.2.9 – ≤ 7.2.*
  • unaffected 7.3 – ≤ *

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2026-103554 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-98640](https://cveledger.app/badge/CVE-2026-98640.svg)](https://cveledger.app/cve/CVE-2026-98640)

Record last updated 19 Oct 2026, 09:23 UTC.