CVE-2026-89722

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
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:

PCI/sysfs: Fix out-of-bounds read in pci_write_legacy_io()

pci_write_legacy_io() loads 4 bytes from the kernfs write buffer regardless of how many bytes userspace wrote:

if (count != 1 && count != 2 && count != 4) return -EINVAL;

return pci_legacy_write(bus, off, *(u32 *)buf, count);

kernfs_fop_write_iter() allocates the buffer with kmalloc(len + 1), so a 1-byte write to the legacy_io sysfs file allocates 2 bytes and the unconditional u32 load reads up to 2 bytes past the end of the allocation, which KASAN reports as a slab-out-of-bounds read. Similarly, a 2-byte write overreads by 1 byte.

Thus, read only the number of bytes requested using get_unaligned_le16() and get_unaligned_le32() for the 2 and 4 byte cases, interpreting the buffer as little-endian to match the byte ordering of PCI I/O port space.

The PowerPC implementation previously compensated for the generic code's native-endian 32-bit load by shifting the value into place for the 1 and 2 byte cases. The shifts were only correct on big-endian kernels.

On little-endian PowerPC (POWER8 and later), they extracted the wrong bytes, so a 1-byte write wrote an out-of-bounds byte instead of the requested value. On big-endian, the native load also caused out_le16() and out_le32() to reverse the user's bytes on the wire for 2 and 4 byte writes. The little-endian helpers resolve both issues, so the shifts are removed.

No changes are needed for the Alpha platform.

The legacy_io file is root-only and exists only on Alpha and PowerPC, the two architectures that define HAVE_PCI_LEGACY.

CVSS v3
—
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
9th
KEV
Not listed

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.

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

September 11, 2026

Last Modified

September 13, 2026

Vendor Advisories for CVE-2026-89722(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 48× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 59 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-12 14:48 UTCEG score recompute
  4. 2026-10-11 19:15 UTCEG score recompute
  5. 2026-10-11 16:31 UTCEG score recompute
  6. 2026-10-11 14:20 UTCVendor advisory
  7. 2026-10-11 14:20 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-11 13:47 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-08 09:41 UTCVendor advisory
  14. 2026-10-08 09:41 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-05 06:33 UTCVendor advisory
  19. 2026-10-05 06:33 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-02 03:24 UTCVendor advisory
  22. 2026-10-02 03:24 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  23. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-29 00:11 UTCEG score recompute
Show 33 more
  1. 2026-09-29 00:11 UTCVendor advisory
  2. 2026-09-29 00:11 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  3. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-09-25 21:02 UTCVendor advisory
  7. 2026-09-25 21:02 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  8. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-09-22 16:50 UTCVendor advisory
  11. 2026-09-22 16:50 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  12. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-09-19 13:36 UTCVendor advisory
  16. 2026-09-19 13:36 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-16 10:27 UTCVendor advisory
  21. 2026-09-16 10:27 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-13 07:18 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  26. 2026-09-13 07:18 UTCNVD update
  27. 2026-09-13 06:49 UTCEG score recompute
  28. 2026-09-13 06:49 UTCGHSA enrichmentGHSA-chvm-2qwm-x2xc
  29. 2026-09-13 06:41 UTCMITRE cvelistV5
  30. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-09-11 20:36 UTCNVD update
  32. 2026-09-11 19:54 UTCEG score recompute
  33. 2026-09-11 19:53 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89722?
CVE-2026-89722 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: PCI/sysfs: Fix out-of-bounds read in pciwritelegacy_io() pciwritelegacy_io() loads 4 bytes from the kernfs write buffer regardless of how many bytes userspace wrote: if (count != 1 && count != 2 && count != 4) return -EINVAL;…
When was the CVE record for CVE-2026-89722 published?
The CVE record for CVE-2026-89722 was published on September 11, 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 September 13, 2026; the record at its source may have been updated since.
Is CVE-2026-89722 actively exploited?
CVE-2026-89722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89722?
A fix for CVE-2026-89722 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89722 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-89722

Explore →

Is Your Infrastructure Affected by CVE-2026-89722?

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