CVE-2026-98640: HID: amd_sfh: Validate PCI BAR size before mapping
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 5f9e2ecb725adced013fbf5f94b9f185fad2e7d9, 5ff24aa7af0bca0780fe4e6effce902065f2c0a7, 65bcc5f89704efe5b9d69d4ea2c1002d90c31382; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 5f9e2ecb725adced013fbf5f94b9f185fad2e7d9, 5ff24aa7af0bca0780fe4e6effce902065f2c0a7, 65bcc5f89704efe5b9d69d4ea2c1002d90c31382; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.11affected
- 4f567b9f8141a86c7d878fadf136e5d1408e3e61 and later · before 92bf2883da0306ab9d1eb794acd1058fc5088ebcaffected · git
- 4f567b9f8141a86c7d878fadf136e5d1408e3e61 and later · before 7b3747d77767f066ccf4a9e8e3a8381643ab5368affected · git
- 4f567b9f8141a86c7d878fadf136e5d1408e3e61 and later · before 5ff24aa7af0bca0780fe4e6effce902065f2c0a7affected · git
- 4f567b9f8141a86c7d878fadf136e5d1408e3e61 and later · before dc687489131559ee52f447592f6d039a5a013061affected · git
- 4f567b9f8141a86c7d878fadf136e5d1408e3e61 and later · before 5f9e2ecb725adced013fbf5f94b9f185fad2e7d9affected · git
- 4f567b9f8141a86c7d878fadf136e5d1408e3e61 and later · before ee25833f037fa22d23ffdbfeebabe3579e8a0346affected · git
- 4f567b9f8141a86c7d878fadf136e5d1408e3e61 and later · before 65bcc5f89704efe5b9d69d4ea2c1002d90c31382affected · git
- before 5.11not affected · semver
- 5.15.222 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98638Oct 18, 2026 · KVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()0Monitor
- ← EarlierCVE-2026-98639Oct 18, 2026 · KVM: riscv: Fix NACL hfence entry update order0Monitor
- Later →CVE-2026-98641Oct 18, 2026 · bpf, arm64: set up the frame pointer for the exception callback0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5f9e2ecb725adced013fbf5f94b9f185fad2e7d9 | Vendor (CNA) |
| Linux Linux | 5ff24aa7af0bca0780fe4e6effce902065f2c0a7 | Vendor (CNA) |
| Linux Linux | 65bcc5f89704efe5b9d69d4ea2c1002d90c31382 | Vendor (CNA) |
| Linux Linux | 7b3747d77767f066ccf4a9e8e3a8381643ab5368 | Vendor (CNA) |
| Linux Linux | 92bf2883da0306ab9d1eb794acd1058fc5088ebc | Vendor (CNA) |
| Linux Linux | dc687489131559ee52f447592f6d039a5a013061 | Vendor (CNA) |
| Linux Linux | ee25833f037fa22d23ffdbfeebabe3579e8a0346 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/5ff24aa7af0bca0780fe4e6effce902065f2c0a7
- git.kernel.org/stable/c/65bcc5f89704efe5b9d69d4ea2c1002d90c31382
- git.kernel.org/stable/c/7b3747d77767f066ccf4a9e8e3a8381643ab5368
- git.kernel.org/stable/c/92bf2883da0306ab9d1eb794acd1058fc5088ebc
- git.kernel.org/stable/c/dc687489131559ee52f447592f6d039a5a013061
- git.kernel.org/stable/c/ee25833f037fa22d23ffdbfeebabe3579e8a0346
Vendor advisories and official records. Exploit/PoC links are deliberately left out.