GHSA-5M32-W674-2XQ4
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In 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: 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.
{
"affected": [],
"aliases": [
"CVE-2026-98640"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:17Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: amd_sfh: Validate PCI BAR size before mapping\n\nThe amd_sfh driver maps PCI BAR 2 using pcim_iomap_regions() and\nsubsequently accesses MMIO registers at offsets up to 0x10958 (e.g.,\nAMD_P2C_MSG3 at 0x1068C). However, the driver never validates that the BAR\nsize is large enough to cover these accesses. If the driver is bound to a\ndevice with a smaller BAR 2, this leads to an out-of-bounds memory access\nand a page fault during the probe function.\n\nFor example, a page fault can occur when reading from privdata-\u003emmio +\nAMD_P2C_MSG3 in mp2_select_ops():\n\n BUG: unable to handle page fault for address: ffffc9000390368c\n PGD 100000067 P4D 100000067 PUD 1012c1067 PMD 105b64067 PTE 0\n Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n RIP: 0010:readl arch/x86/include/asm/io.h:59 [inline]\n RIP: 0010:mp2_select_ops drivers/hid/amd-sfh-hid/amd_sfh_pcie.c:282\n [inline]\n RIP: 0010:amd_mp2_pci_probe+0x337/0x5f0\n drivers/hid/amd-sfh-hid/amd_sfh_pcie.c:487\n Call Trace:\n \u003cTASK\u003e\n local_pci_probe drivers/pci/pci-driver.c:332 [inline]\n pci_call_probe drivers/pci/pci-driver.c:394 [inline]\n __pci_device_probe drivers/pci/pci-driver.c:455 [inline]\n pci_device_probe+0x431/0xc90 drivers/pci/pci-driver.c:489\n\nFix this by verifying that the length of BAR 2 is at least 128KB before\nattempting to map it. Since the maximum accessed offset is 0x10958, and PCI\nBAR sizes are powers of 2, any legitimate hardware will have a BAR size of\nat least 128KB.",
"id": "GHSA-5m32-w674-2xq4",
"modified": "2026-10-18T18:31:57Z",
"published": "2026-10-18T18:31:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98640"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5f9e2ecb725adced013fbf5f94b9f185fad2e7d9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5ff24aa7af0bca0780fe4e6effce902065f2c0a7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/65bcc5f89704efe5b9d69d4ea2c1002d90c31382"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7b3747d77767f066ccf4a9e8e3a8381643ab5368"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/92bf2883da0306ab9d1eb794acd1058fc5088ebc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dc687489131559ee52f447592f6d039a5a013061"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee25833f037fa22d23ffdbfeebabe3579e8a0346"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.