CVE-2026-89956: s390/vfio-ap: Fix missing lock required to access list of ap_matrix_mdev objects

Received
AliasesUBUNTU-CVE-2026-89956DEBIAN-CVE-2026-89956
Published 16-09-2026Last modified 30-10-2026

Vulnerability summary

CVE-2026-89956 is a vulnerability in linux with no CVSS score yet. EPSS estimates a 0.23% chance of exploitation in the next 30 days, higher than 13.7% of scored vulnerabilities.

Priority
Insufficient evidence

No CVSS vector published; no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
Not scored
010
No CVSS score recorded
EPSS score
0.23%
0%100%
Low · +0.02 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 25 · Related 17

Timeline

  1. 16-09-2026
    PublishedVulnerability first disclosed.
  2. 30-10-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

Risk metrics not yet published.

EPSS trend

Probability

0.23%

Chance of exploitation in the next 30 days

Percentile

14%

Versus all other CVEs

30-day change

Increase +0.02 pp

From 0.21% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: not stated in public data.

Ubuntu142 products
  • linuxAll versions (No fix recorded) | < 6.8.0-149.149 | < 7.0.0-42.42
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1069.74 | < 7.0.0-1016.17
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linuxAll versions (No fix recorded) | < 6.12.113-1 | < 7.2.6-1
  • linux-6.12< 6.12.113-1~deb12u1
Linux1 product
  • linux≥ 2c1ee8983aa377fef4f725162f4f3aa5f9575d4a, < 3ea443510739468238324234eaab0d37922283f5 | ≥ 2c1ee8983aa377fef4f725162f4f3aa5f9575d4a, < 22dc712c170efc1a549e3f872467c880be995ac7 | ≥ 2c1ee8983aa377fef4f725162f4f3aa5f9575d4a, < 530ee1cc71562b6799b9ece187b6c1b757a2c6fa | ≥ 2c1ee8983aa377fef4f725162f4f3aa5f9575d4a, < 647916988272fe5ecb4bb30cd02b51af9960618a | ≥ 2c1ee8983aa377fef4f725162f4f3aa5f9575d4a, < 0fd74477d05743d4cd9b25a3b667daa278d53b93 | ≥ 2c1ee8983aa377fef4f725162f4f3aa5f9575d4a, < 7fa61c29850d05e40ca9ed41bfdf57673023f581 | 6.0

3 vendors · 145 products

References

25 links
Show all 25 references