cve.bz

CVE-2026-97989 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.114
  • Linux Linux: fixed in 6.18.57
  • Linux Linux: fixed in 7.2.7
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-97989 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97989?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97989?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97989 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.15 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.114
Linux6.186.18.57
Linux7.27.2.7
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linuxno fix listedDEBIAN-CVE-2026-97989
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-97989
Debian13linux6.12.115-2DEBIAN-CVE-2026-97989
Debian14linux7.2.7-1DEBIAN-CVE-2026-97989
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-97989
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-97989
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-97989
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-97989
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 44 moreno fix listedUBUNTU-CVE-2026-97989
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-97989 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-97989 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-97989 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-97989 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-97989 USN-9020-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-97989
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-97989 USN-8959-1
16 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.9-1.1openSUSE-SU-2026:12074-1
Azure Linux3kernel6.6.161.1-1AZL-104751
Alpaquita23linux-ltsno fix listedBELL-CVE-2026-97989
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-97989
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-97989

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low impact flaw was found in the Linux kernel's vDPA Device in Userspace (VDUSE) subsystem. In Red Hat product streams that include the VDUSE subsystem (Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS, and OpenShift Container Platform releases shipping affected RHEL 9-based kernels), the driver does not properly validate virtqueue alignment parameters during device configuration: vduse_validate_config() only checks the upper bound of vq_align, so zero or non-power-of-two alignment values can reach the virtio ring helpers, leaving the used ring pointer NULL. A local user with the administrative privileges required to create and configure VDUSE devices could supply an invalid alignment value when creating a device, and bringing the resulting virtio-net device up triggers a NULL pointer dereference in virtqueue_kick_prepare_split(), crashing the kernel and causing a denial of service. Red Hat product streams that do not contain the VDUSE subsystem, such as earlier Red Hat Enterprise Linux versions and minor streams, are not affected because the vulnerable code is not present. Although the Red Hat CVSS 3.1 base score is 5.5 (Moderate), Red Hat assesses the overall impact of this flaw as Low because exploitation requires local administrative privileges and only availability is affected, with no confidentiality or integrity impact. The fix is currently deferred for the affected streams; the residual risk is limited to a locally privileged user triggering a kernel crash and denial of service.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97989.

References

Check your stackJSON