CVE-2026-89795

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

PCI: Allow per function PCI slots to fix slot reset on s390

On s390 systems, which use a machine level hypervisor, PCI devices are always accessed through a form of PCI pass-through which fundamentally operates on a per PCI function granularity. This is also reflected in the s390 PCI hotplug driver which creates hotplug slots for individual PCI functions. Its reset_slot() function, which is a wrapper for zpci_hot_reset_device(), thus also resets individual functions.

Currently, the pci_create_slot() assigns the same pci_slot object to multifunction devices. This approach worked fine on s390 systems that only exposed virtual functions as individual PCI domains to the operating system. Since commit 44510d6fa0c0 ("s390/pci: Handling multifunctions") s390 supports exposing the topology of multifunction PCI devices by grouping them in a shared PCI domain. This creates a problem when resetting a function through the hotplug driver's slot_reset() interface.

When attempting to reset a function through the hotplug driver, the shared slot assignment causes the wrong function to be reset instead of the intended one. It also leaks memory as we do create a pci_slot object for the function, but don't correctly free it in pci_slot_release().

Add a flag for struct pci_slot to allow per function PCI slots for functions managed through a hypervisor, which exposes individual PCI functions while retaining the topology. Since we can use all 8 bits for slot 'number' (for ARI devices), change slot 'number' u16 to account for special values PCI_SLOT_PLACEHOLDER and PCI_SLOT_ALL_DEVICES.

CVSS v3
8.4
EG Score
8.4HIGHhigh confidence
EG Risk
42
EG Risk 42/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

PCI: Allow per function PCI slots to fix slot reset on s390 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dcc5bec09e23bbc4f9de055a11fce9937244f2c8
generic

PCI: Allow per function PCI slots to fix slot reset on s390 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ecdcceed4d377b02d4ea036b65f83f962c38ede7
generic

PCI: Allow per function PCI slots to fix slot reset on s390 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2050d900f9adbd6d6f38d30e182bcd9ad3108467

Vendor Advisories for CVE-2026-89795(2)

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 (360 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 (183 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 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 47× in last 7d / 125× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 125 total refreshes for this CVE.

  1. 2026-10-05 07:00 UTCEG score recompute
  2. 2026-10-05 07:00 UTCVendor advisory
  3. 2026-10-05 07:00 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 20:10 UTCVendor advisory
  6. 2026-10-04 20:09 UTCGHSA enrichment
  7. 2026-10-04 09:17 UTCVendor advisory
  8. 2026-10-04 09:17 UTCGHSA enrichment
  9. 2026-10-03 22:26 UTCEG score recompute
  10. 2026-10-03 22:26 UTCVendor advisory
  11. 2026-10-03 22:26 UTCGHSA enrichment
  12. 2026-10-03 11:34 UTCVendor advisory
  13. 2026-10-03 11:34 UTCGHSA enrichment
  14. 2026-10-03 10:25 UTCVendor advisory
  15. 2026-10-03 10:25 UTCGHSA enrichment
  16. 2026-10-02 23:34 UTCEG score recompute
  17. 2026-10-02 23:34 UTCVendor advisory
  18. 2026-10-02 23:34 UTCGHSA enrichment
  19. 2026-10-02 12:26 UTCVendor advisory
  20. 2026-10-02 12:26 UTCGHSA enrichment
  21. 2026-10-02 01:28 UTCEG score recompute
  22. 2026-10-02 01:28 UTCVendor advisory
  23. 2026-10-02 01:28 UTCGHSA enrichment
  24. 2026-10-01 19:51 UTCEPSS rescore
  25. 2026-10-01 14:38 UTCVendor advisory
Show 75 more
  1. 2026-10-01 14:38 UTCGHSA enrichment
  2. 2026-10-01 03:48 UTCVendor advisory
  3. 2026-10-01 03:48 UTCGHSA enrichment
  4. 2026-09-30 16:58 UTCEG score recompute
  5. 2026-09-30 16:58 UTCVendor advisory
  6. 2026-09-30 16:58 UTCGHSA enrichment
  7. 2026-09-30 15:04 UTCEPSS rescore
  8. 2026-09-30 05:37 UTCVendor advisory
  9. 2026-09-30 05:37 UTCGHSA enrichment
  10. 2026-09-29 18:45 UTCEG score recompute
  11. 2026-09-29 18:45 UTCVendor advisory
  12. 2026-09-29 18:45 UTCGHSA enrichment
  13. 2026-09-29 07:48 UTCEG score recompute
  14. 2026-09-29 07:48 UTCVendor advisory
  15. 2026-09-29 07:48 UTCGHSA enrichment
  16. 2026-09-28 20:58 UTCEG score recompute
  17. 2026-09-28 20:58 UTCVendor advisory
  18. 2026-09-28 20:58 UTCGHSA enrichment
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 13:52 UTCEPSS rescore
  21. 2026-09-28 10:07 UTCVendor advisory
  22. 2026-09-28 10:07 UTCGHSA enrichment
  23. 2026-09-27 23:13 UTCEG score recompute
  24. 2026-09-27 23:13 UTCVendor advisory
  25. 2026-09-27 23:13 UTCGHSA enrichment
  26. 2026-09-27 13:49 UTCEPSS rescore
  27. 2026-09-27 12:22 UTCVendor advisory
  28. 2026-09-27 12:22 UTCGHSA enrichment
  29. 2026-09-27 01:32 UTCEG score recompute
  30. 2026-09-27 01:32 UTCVendor advisory
  31. 2026-09-27 01:32 UTCGHSA enrichment
  32. 2026-09-26 15:59 UTCEPSS rescore
  33. 2026-09-26 14:39 UTCVendor advisory
  34. 2026-09-26 14:39 UTCGHSA enrichment
  35. 2026-09-26 03:34 UTCEG score recompute
  36. 2026-09-26 03:34 UTCVendor advisory
  37. 2026-09-26 03:34 UTCGHSA enrichment
  38. 2026-09-25 16:35 UTCVendor advisory
  39. 2026-09-25 16:35 UTCGHSA enrichment
  40. 2026-09-25 05:45 UTCVendor advisory
  41. 2026-09-25 05:45 UTCGHSA enrichment
  42. 2026-09-24 18:54 UTCEG score recompute
  43. 2026-09-24 18:54 UTCVendor advisory
  44. 2026-09-24 18:54 UTCGHSA enrichment
  45. 2026-09-24 14:04 UTCEPSS rescore
  46. 2026-09-24 08:04 UTCVendor advisory
  47. 2026-09-24 08:04 UTCGHSA enrichment
  48. 2026-09-23 21:14 UTCEG score recompute
  49. 2026-09-23 21:14 UTCVendor advisory
  50. 2026-09-23 21:14 UTCGHSA enrichment
  51. 2026-09-23 17:54 UTCEPSS rescore
  52. 2026-09-23 10:24 UTCVendor advisory
  53. 2026-09-23 10:24 UTCGHSA enrichment
  54. 2026-09-22 23:34 UTCEG score recompute
  55. 2026-09-22 23:34 UTCVendor advisory
  56. 2026-09-22 23:33 UTCGHSA enrichment
  57. 2026-09-22 16:01 UTCEPSS rescore
  58. 2026-09-22 12:37 UTCVendor advisory
  59. 2026-09-22 12:37 UTCGHSA enrichment
  60. 2026-09-22 01:47 UTCEG score recompute
  61. 2026-09-22 01:47 UTCVendor advisory
  62. 2026-09-22 01:47 UTCGHSA enrichment
  63. 2026-09-21 21:09 UTCEPSS rescore
  64. 2026-09-21 14:55 UTCVendor advisory
  65. 2026-09-21 14:54 UTCGHSA enrichment
  66. 2026-09-21 03:48 UTCEG score recompute
  67. 2026-09-21 03:48 UTCVendor advisory
  68. 2026-09-21 03:48 UTCGHSA enrichment
  69. 2026-09-20 20:16 UTCEPSS rescore
  70. 2026-09-20 16:58 UTCVendor advisory
  71. 2026-09-20 16:58 UTCGHSA enrichment
  72. 2026-09-20 06:07 UTCVendor advisory
  73. 2026-09-20 06:07 UTCGHSA enrichment
  74. 2026-09-19 19:17 UTCEG score recompute
  75. 2026-09-19 19:17 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-89795?
CVE-2026-89795 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: PCI: Allow per function PCI slots to fix slot reset on s390 On s390 systems, which use a machine level hypervisor, PCI devices are always accessed through a form of PCI pass-through which fundamentally operates on a per PCI…
When was CVE-2026-89795 disclosed?
CVE-2026-89795 was first published on September 16, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89795 actively exploited?
CVE-2026-89795 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89795?
CVE-2026-89795 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89795?
No fix for CVE-2026-89795 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-89795 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-89795

Explore →

Is Your Infrastructure Affected by CVE-2026-89795?

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