cve.bz

CVE-2026-89956 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: s390/vfio-ap: Fix missing lock required to access list of ap_matrix_mdev objects In order to traverse or add/remove ap_matrix_mdev objects in the matrix_dev->mdev_list, the matrix_dev->guests_lock mutex must be held. There are two functions that access the list without holding the mutex: vfio_ap_mdev_probe function ~~~~~~~~~~~~~~~~~~~~~~~~~~~ The vfio_ap_mdev_probe function uses the matrix_dev->mdevs_lock mutex to guard the add of a newly created ap_matrix_mdev object to the matrix_dev->mdev_list. This mutex does not protect list access; its purpose is to guard against concurrent access to fields contained in an ap_matrix_mdev object. This could lead to kernel memory corruption or use-after-free if another mdev is created or removed concurrently. The adding of an ap_matrix_mdev object to matrix_dev->mdev_list is now guarded by the matrix_dev->guests_lock which is the correct way to protect against concurrent mdev_list access. Also removed the following two lines of code because the matrix_mdev is allocated via vfio_alloc_device macro which uses kzalloc, so req_trigger and cfg_chg_trigger are already zero-initialised when the struct is allocated before the call to vfio_register_emulated_iommu_dev. This prevents a window whereby these triggers are set to NULL after the device is exposed to userspace. matrix_mdev->req_trigger = NULL; matrix_mdev->cfg_chg_trigger = NULL; vfio_ap_mdev_for_queue function ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The status_show function that supports display of the status attribute of the devices in /sys/bus/ap/devices calls the vfio_ap_mdev_for_queue function which iterates the matrix_dev->mdev_list to find the object representing the queue device whose status is to be displayed. In order to traverse this list, the matrix_dev->guests_lock mutex must be held. To fix this, the guests_lock mutex is taken prior to taking the matrix_dev->mdevs_lock mutex in the status_show function. It is taken there rather than the vfio_ap_mdev_for_queue function - where it is needed - because it must be taken prior to the mdevs_lock mutex in order to adhere to the proper locking order and prevent a lockdep splat; also because the mdevs_lock is needed there to access fields within the matrix_mdev object in that function. See the vfio-ap-locking.rst in the linux kernel tree.
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; 14th 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.1.191
  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.112
  • Linux Linux: fixed in 6.18.51
  • Linux Linux: fixed in 7.2.5
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Red Hat, openSUSE, Rocky Linux, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-89956 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89956?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89956?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-89956 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
Linux6.0 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.160
Linux6.126.12.112
Linux6.186.18.51
Linux7.27.2.5
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linuxno fix listedDEBIAN-CVE-2026-89956
Debian12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-89956
Debian13linux6.12.113-1DEBIAN-CVE-2026-89956
Debian14linux7.2.6-1DEBIAN-CVE-2026-89956
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89956
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89956
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89956
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-89956 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-89956 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-89956 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-89956 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-89956 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-89956 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-89956 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-89956 USN-9025-1
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 moreno fix listedUBUNTU-CVE-2026-89956
43 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 31 more0:5.14.0-741.22.1.el9_9RHSA-2026:99135
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 47 more0:5.14.0-741.22.1.el9_9RHSA-2026:99135
Red Hatenterprise_linux:9::crblibperf, rv-debuginfo, perf-debuginfo and 18 more0:5.14.0-741.22.1.el9_9RHSA-2026:99135
Red Hatenterprise_linux:9::nfvkernel-rt, rv-debuginfo, kernel-rt-core and 25 more0:5.14.0-741.22.1.el9_9RHSA-2026:99135
Red Hatenterprise_linux:9::realtimekernel-rt, rv-debuginfo, kernel-rt-64k and 37 more0:5.14.0-741.22.1.el9_9RHSA-2026:99135
Red Hatenterprise_linux:10.3rv, perf, rtla and 89 more0:6.12.0-264.16.1.el10_3RHSA-2026:99133
Red Hatenterprise_linux_eus:10.2rv, perf, rtla and 87 more0:6.12.0-211.75.1.el10_2RHSA-2026:99139
Red Hatrhel_eus:9.8::appstreamrv, perf, rtla and 29 more0:5.14.0-687.67.1.el9_8RHSA-2026:99148
Red Hatrhel_eus:9.8::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-687.67.1.el9_8RHSA-2026:99148
Red Hatrhel_eus:9.8::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-687.67.1.el9_8RHSA-2026:99148
Red Hatrhel_eus:9.8::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-687.67.1.el9_8RHSA-2026:99148
Red Hatrhel_eus:9.8::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-687.67.1.el9_8RHSA-2026:99148
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Rocky Linux9rv, perf, rtla and 88 more0:5.14.0-741.22.1.el9_9RLSA-2026:99135
Rocky Linux10rv, perf, rtla and 89 more0:6.12.0-264.16.1.el10_3RLSA-2026:99133
Azure Linux3kernel6.6.161.1-1AZL-101556
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-89956
Alpaquita25linux-lts6.12.112-r0BELL-CVE-2026-89956
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-89956

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; 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 Moderate.

Red Hat's statement

A race in s390/vfio-ap can occur because matrix_dev mdev_list is modified or traversed without holding the required guests_lock. Concurrent mdev creation removal or status access can corrupt the list state or leave a stale ap_matrix_mdev reference, which makes this a use after free or kernel memory corruption candidate rather than a simple warning. For the CVSS the PR:L is used for the paranoid score because a delegated vfio management user, container root, or service account may be able to exercise mediated device control without full host administration. The issue is local and is not network reachable. Impact is at least local denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to kernel memory corruption, so it should be reviewed manually.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't 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 10kernelAffected
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 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

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

References

Check your stackJSON