cve.bz

CVE-2026-89777 linux linux

8.8 highEPSS 0.2%Fix available

High (8.8) in linux linux. 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: vfio/pci: clear vdev->msi_perm after freeing it on init failure vfio_msi_cap_len() lazily allocates the per-device MSI permission table: vdev->msi_perm = kmalloc_obj(struct perm_bits, GFP_KERNEL_ACCOUNT); if (!vdev->msi_perm) return -ENOMEM; ret = init_pci_cap_msi_perm(vdev->msi_perm, len, flags); if (ret) { kfree(vdev->msi_perm); return ret; /* vdev->msi_perm left dangling */ } When init_pci_cap_msi_perm() -> alloc_perm_bits() fails with -ENOMEM, the error path frees vdev->msi_perm but leaves the freed pointer stored in it. vdev->msi_perm is not re-zeroed later because struct vfio_pci_core_device is per-device and persists across open/close cycles, and the vfio_config_init() error path returns without calling vfio_config_free(). So the dangling pointer outlives the failed open. That leads to two use-after-frees on the same device: 1. Reuse. The next vfio_config_init() sees the stale pointer at "if (vdev->msi_perm) return len;" and reuses the freed object. MSI config accesses in vfio_pci_config_rw_single() then dereference and call the freed perm->readfn / perm->writefn function pointers. 2. Double free. A later vfio_config_free() runs free_perm_bits() and kfree() on the already-freed object. Fix it by NULLing vdev->msi_perm after the kfree(), matching the NULL-after-free discipline already used in free_perm_bits() and vfio_config_free(). BUG: KASAN: slab-use-after-free in vfio_pci_config_rw_single (drivers/vfio/pci/vfio_pci_config.c:1961) Read of size 8 at addr ffff88800fcc88d0 by task exploit/143 Call Trace: ... kasan_report (mm/kasan/report.c:595) vfio_pci_config_rw_single (drivers/vfio/pci/vfio_pci_config.c:1961) vfio_pci_config_rw (drivers/vfio/pci/vfio_pci_config.c:1986) vfio_pci_rw (drivers/vfio/pci/vfio_pci_core.c:1599) vfs_read (fs/read_write.c:572) __x64_sys_pread64 (fs/read_write.c:764) do_syscall_64 (arch/x86/entry/syscall_64.c:94) ... Followed on device close by a double free of the same object: Oops: general protection fault, probably for non-canonical address 0x1f63e0e8000008: 0000 [#1] SMP KASAN NOPTI RIP: 0010:kfree (mm/slub.c:6711) Call Trace: vfio_config_free (drivers/vfio/pci/vfio_pci_config.c:1861) vfio_pci_core_disable (drivers/vfio/pci/vfio_pci_core.c:685) vfio_pci_core_close_device (drivers/vfio/pci/vfio_pci_core.c:777) vfio_df_close (drivers/vfio/vfio_main.c:602) vfio_device_fops_release (drivers/vfio/vfio_main.c:648) __fput (fs/file_table.c:512) __x64_sys_close (fs/open.c:1496) do_syscall_64 (arch/x86/entry/syscall_64.c:94) ... Kernel panic - not syncing: Fatal exception

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 5.10.270
  • Linux Linux: fixed in 5.15.221
  • Linux Linux: fixed in 6.1.188
  • Linux Linux: fixed in 6.6.157
  • Linux Linux: fixed in 6.12.110
  • Linux Linux: fixed in 6.18.52
  • Linux Linux: fixed in 7.2.6
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Red Hat, openSUSE, AlmaLinux, Rocky Linux, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-89777 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89777?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89777?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-89777 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
Linuxfrom 4.4.203 before 4.5
Linuxfrom 4.9.203 before 4.10
Linuxfrom 4.14.155 before 4.15
Linuxfrom 4.19.85 before 4.20
Linux4.20 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.270
Linux5.155.15.221
Linux6.16.1.188
Linux6.66.6.157
Linux6.126.12.110
Linux6.186.18.52
Linux7.27.2.6
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-89777
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-89777
Debian13linux6.12.111-1DEBIAN-CVE-2026-89777
Debian14linux7.2.6-1DEBIAN-CVE-2026-89777
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89777
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89777
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89777
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-89777 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-89777 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-89777 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-89777 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-89777 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-89777 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-89777 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-89777 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-89777 USN-9024-1
82 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:8::baseosperf, kernel, bpftool and 30 more0:4.18.0-553.177.1.el8_10RHSA-2026:87375
Red Hatenterprise_linux:8::crbperf-debuginfo, kernel-debuginfo, bpftool-debuginfo and 7 more0:4.18.0-553.177.1.el8_10RHSA-2026:87375
Red Hatenterprise_linux:8::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 12 more0:4.18.0-553.177.1.rt7.518.el8_10RHSA-2026:87374
Red Hatenterprise_linux:8::realtimekernel-rt, kernel-rt-core, kernel-rt-debug and 10 more0:4.18.0-553.177.1.rt7.518.el8_10RHSA-2026:87374
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 31 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 47 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::crblibperf, rv-debuginfo, perf-debuginfo and 18 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-687.61.1.el9_8RHSA-2026:90365
Red Hatenterprise_linux:9::nfvkernel-rt, rv-debuginfo, kernel-rt-core and 25 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
5 more for Red Hat in the JSON and on Red Hat's page.
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
AlmaLinux8kernel-rt, kernel-rt-core, kernel-rt-debug and 7 more4.18.0-553.177.1.rt7.518.el8_10ALSA-2026:87374
AlmaLinux8perf, kernel, bpftool and 22 more4.18.0-553.177.1.el8_10ALSA-2026:87375
AlmaLinux9rv, perf, rtla and 71 more5.14.0-687.61.1.el9_8ALSA-2026:90365
AlmaLinux10rv, perf, rtla and 72 more6.12.0-211.69.1.el10_2ALSA-2026:91565
Rocky Linux8kernel0:4.18.0-553.177.1.el8_10RLSA-2026:87375
Rocky Linux8kernel-rt0:4.18.0-553.177.1.rt7.518.el8_10RLSA-2026:87374
Rocky Linux9kernel0:5.14.0-687.61.1.el9_8RLSA-2026:90365
Rocky Linux9kernel0:5.14.0-687.61.1.el9_8.cloud.1.0RXSA-2026:90365
Rocky Linux9rv, perf, rtla and 88 more0:5.14.0-741.20.1.el9_9RLSA-2026:97873
Rocky Linux10kernel0:6.12.0-211.69.1.el10_2RLSA-2026:91565
Azure Linux3kernel6.6.157.1-1AZL-101571
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-89777
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-89777
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-89777

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; 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 · Red Hat · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A use-after-free and double-free flaw in the Linux kernel's vfio/pci subsystem has been rated Important by Red Hat. When initialization of the per-device MSI permission table fails (for example, when an underlying allocation fails with -ENOMEM), the error path in vfio_msi_cap_len() frees vdev->msi_perm but leaves the dangling pointer stored in the per-device vfio_pci_core_device structure, which persists across open/close cycles. A local attacker with access to a VFIO PCI device could trigger this failed initialization path and then, on a subsequent open or close of the device, cause the freed object to be reused for MSI config-space accesses (dereferencing and calling the freed perm->readfn/perm->writefn function pointers) or to be freed a second time in vfio_config_free(). This can lead to a kernel panic and system crash (denial of service) or potentially to execution of arbitrary code with elevated privileges. Red Hat rates this flaw as Important with a CVSS 3.1 score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H); the higher CVE.org score of 8.8 reflects a lower attack-complexity assessment, whereas Red Hat considers exploitation to depend on reliably steering a memory-allocation failure during device initialization. Within Red Hat's affected product scope, Red Hat Enterprise Linux 6 and 7 (kernel and kernel-rt ELS streams) are not affected because the vulnerable code is not present, while the vulnerable code is present in Red Hat Enterprise Linux 8, 9, and 10 (kernel and kernel-rt), Red Hat In-Vehicle OS, and Red Hat OpenShift versions that ship an affected kernel, and fixes are being pursued through the responsible engineering teams.

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 10kernel-0:6.12.0-211.69.1.el10_2Fixed 2026-10-28RHSA-2026:91565
Red Hat Enterprise Linux 10kernel-0:6.12.0-264.14.1.el10_3Fixed 2026-11-11RHSA-2026:98608
Red Hat Enterprise Linux 8kernel-rt-0:4.18.0-553.177.1.rt7.518.el8_10Fixed 2026-10-21RHSA-2026:87374
Red Hat Enterprise Linux 8kernel-0:4.18.0-553.177.1.el8_10Fixed 2026-10-21RHSA-2026:87375
Red Hat Enterprise Linux 9kernel-0:5.14.0-687.61.1.el9_8Fixed 2026-10-26RHSA-2026:90365
Red Hat Enterprise Linux 9kernel-0:5.14.0-741.20.1.el9_9Fixed 2026-11-11RHSA-2026:97873
Red Hat OpenShift Container Platform 4.22openshift/ose-rhel-coreos-9:4.22.9.8.202611032353-0Fixed 2026-11-06RHSA-2026:95346
Red Hat OpenShift Container Platform 5.0openshift/ose-rhel-coreos-9:5.0.10.2.202611022203-0Fixed 2026-11-09RHSA-2026:94537
Shadow Migration Toolkit for Virtualization for RHEL 10kernel-0:6.12.0-211.69.1.el10_2Fixed 2026-10-28RHSA-2026:91565
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected

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

References

Check your stackJSON