CVE-2026-93238

s390/vfio-ap: fix potential use of uninitialized apm_filtered bitmap

N/A
Published: September 24, 2026 at 03:34 PM UTC
Updated: October 19, 2026 at 10:17 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 potential use of uninitialized apm_filtered bitmap The DECLARE_BITMAP(apm_filtered, AP_DEVICES) macro allocates the bitmap on the stack without zero-initializing it. In vfio_ap_mdev_hot_plug_cfg(), the vfio_ap_mdev_filter_matrix() function is only called to initialize and populate apm_filtered if either filter_adapters or filter_domains is true. If the hot plug configuration change only adds control domains (meaning filter_cdoms is true, but filter_adapters and filter_domains are both false), vfio_ap_mdev_filter_matrix() is bypassed. Consequently, apm_filtered is passed to reset_queues_for_apids() with uninitialized stack garbage. This can cause reset_queues_for_apids() to interpret arbitrary stack garbage bits as valid APIDs to reset, potentially performing unintended guest hardware queue resets. Fix this by zero-initializing the apm_filtered bitmap at the beginning of vfio_ap_mdev_hot_plug_cfg() using bitmap_zero().

Affected

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

6.0eeb386aeb5b7c8d2dae6a3ba49255d8a97803182
Vendor states this is fixed in 09548edc6114f1eb1035b30795e893204ef45b85 (fixed)
Vendor states this is fixed in 4ba8a08f5f26ed59f356a6318bca3aa7cc0af3e2 (fixed)
Vendor states this is fixed in 6d554f2571e6b4db242593ba561efd6a6d1f99a9 (fixed)
Vendor states this is fixed in bf09b9d7cd7890bc3a3b7eb63d5ece15f88bfde7 (fixed)
Vendor states this is fixed in f73db632524320d2b93bc8534be8ea875053502d (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