CVE-2026-89955

s390/vfio-ap: Fix NULL deref in status_show() during queue probe

N/A
Published: September 16, 2026 at 10:32 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix NULL deref in status_show() during queue probe When vfio_ap_mdev_probe_queue() creates the sysfs attribute group, the queue's driver data has not yet been set. A concurrent read of the 'status' attribute can therefore call dev_get_drvdata() and get NULL, which is then passed directly to vfio_ap_mdev_for_queue() where q->apqn is unconditionally dereferenced, causing a NULL pointer dereference. Fix this by acquiring the update locks before calling sysfs_create_group(). The status_show() function acquires guests_lock before reading the driver data, so any concurrent read will block until after dev_set_drvdata() has been called and the update locks are released. As a bonus, the APQN no longer needs to be read from the queue struct after allocation — it can be read directly from apdev before allocation and stored in a local variable, which is then assigned to q->apqn once the allocation succeeds.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

260f3ea141382386e97611e7c2029bc013088ab16.0
Vendor states this is fixed in 31fa0a8a3c337ed2d200166d6926ab23c14f8b2e (fixed)
Vendor states this is fixed in 69632952aca04caa71e49953b6949fc04e788e67 (fixed)
Vendor states this is fixed in 7db2511fc601ca3a6e3fb1bdce02261c3c3167c3 (fixed)
Vendor states this is fixed in dd6f4ef6f8a37412909ad787c837332fb070159c (fixed)
Vendor states this is fixed in e102ce0f4af99dff769a4b1b4daa4cc6bd5ad2d9 (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card