CVE-2026-97989

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

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:

vduse: validate virtqueue alignment

vduse_validate_config() only checks the upper bound of vq_align. Invalid values can therefore reach vring_create_virtqueue_map(). The split-ring helpers use align - 1 as a bit mask, so the alignment must be a non-zero power of two. A zero value makes vring_size() drop the descriptor and available-ring part and vring_init() leave the used ring pointer NULL.

The VIRTIO spec requires the used ring to start at an address aligned to at least 4 bytes. Reject values below VRING_USED_ALIGN_SIZE as well as non-power-of-two values before they reach the virtio ring helpers.

Opening a virtio-net device created with vq_align=0 triggered:

BUG: KASAN: null-ptr-deref in virtqueue_kick_prepare_split+0xe3/0x100 Read of size 2 at addr 0000000000000000 by task systemd-network/1062

Call Trace (relevant frames): dump_stack_lvl print_report kasan_report __asan_load2 virtqueue_kick_prepare_split+0xe3/0x100 virtqueue_kick_prepare+0x40/0x60 try_fill_recv+0x857/0x1250 virtnet_open+0x189/0x460 __dev_open+0x225/0x390 __dev_change_flags+0x368/0x3b0 netif_change_flags+0x56/0xc0 do_setlink.isra.0+0x68c/0x1e30

Validate the value before it reaches the virtio ring helpers.

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
4th
KEV
Not listed

Published

September 25, 2026

Last Modified

September 25, 2026

References (2)

Vendor Advisories for CVE-2026-97989(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 (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 (179 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 15× in last 7d / 20× 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.

  1. 2026-10-05 06:27 UTCVendor advisory
  2. 2026-10-05 06:27 UTCGHSA enrichment
  3. 2026-10-04 23:23 UTCEPSS rescore
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:57 UTCEPSS rescore
  6. 2026-10-02 00:12 UTCEG score recompute
  7. 2026-10-02 00:12 UTCVendor advisory
  8. 2026-10-02 00:12 UTCGHSA enrichment
  9. 2026-10-01 19:51 UTCEPSS rescore
  10. 2026-09-30 15:04 UTCEPSS rescore
  11. 2026-09-28 18:00 UTCEG score recompute
  12. 2026-09-28 18:00 UTCVendor advisory
  13. 2026-09-28 17:59 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-27 13:49 UTCEPSS rescore
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-25 11:30 UTCNVD update
  19. 2026-09-25 10:30 UTCEG score recompute
  20. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-97989?
CVE-2026-97989 is a publicly disclosed vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: vduse: validate virtqueue alignment vdusevalidateconfig() only checks the upper bound of vq_align. Invalid values can therefore reach vringcreatevirtqueue_map(). The split-ring helpers use align - 1 as a bit mask, so the alignment…
When was CVE-2026-97989 disclosed?
CVE-2026-97989 was first published on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97989 actively exploited?
CVE-2026-97989 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-97989?
No fix for CVE-2026-97989 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-97989 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-97989

Explore →

Is Your Infrastructure Affected by CVE-2026-97989?

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

Book a Demo →Browse All CVEs