CVE-2026-98640

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-103554 (ENISA EUVD) · GHSA-5m32-w674-2xq4 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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: 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.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 18, 2026

Last Modified

October 19, 2026

Vendor Advisories for CVE-2026-98640(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(18)

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1, 6.12.111-1~deb12u1
  • every version up to 6.12.113-1~deb12u1: fixed in 6.12.113-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (36 versions)
  • every version up to 6.12.113-1: fixed in 6.12.113-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (184 versions)
  • every version up to 7.2.9-1: fixed in 7.2.9-1
—

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-11-17 20:27 UTCEchelonGraph re-scored
  6. 2026-11-17 20:27 UTCVendor advisory
  7. 2026-11-17 20:27 UTCGHSA enrichmentGHSA-5m32-w674-2xq4
  8. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 19 more
  1. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-28 10:25 UTCOSV refresh
  3. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-25 13:46 UTCEchelonGraph re-scored
  7. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-19 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-19 10:49 UTCGHSA enrichmentGHSA-5m32-w674-2xq4
  14. 2026-10-19 10:26 UTCNVD update
  15. 2026-10-19 10:02 UTCGHSA enrichmentGHSA-5m32-w674-2xq4
  16. 2026-10-19 09:39 UTCMITRE cvelistV5
  17. 2026-10-18 16:25 UTCNVD update
  18. 2026-10-18 15:29 UTCEchelonGraph re-scored
  19. 2026-10-18 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-98640?
CVE-2026-98640 is a vulnerability whose severity is not yet rated; its CVE record was published on October 18, 2026. 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…
When was the CVE record for CVE-2026-98640 published?
The CVE record for CVE-2026-98640 was published on October 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-98640 actively exploited?
CVE-2026-98640 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-98640?
A fix for CVE-2026-98640 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98640 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98640

Explore →

Is Your Infrastructure Affected by CVE-2026-98640?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.