{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93238 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93238 is an use after free vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93238 and fix it if it is affected.\n\nWhat it is: CVE-2026-93238 is an use after free vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93238 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93238/ (Markdown: https://insights.sbomify.com/CVE-2026-93238/index.md)","id":"CVE-2026-93238","markdown":"https://insights.sbomify.com/CVE-2026-93238/index.md","name":"CVE-2026-93238","record":{"aliases":["BELL-CVE-2026-93238","DEBIAN-CVE-2026-93238","GHSA-q4pw-hxg7-r6v7","UBUNTU-CVE-2026-93238"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local attacker with high privileges can trigger unintended guest hardware queue resets in the Linux kernel s390/vfio-ap driver due to uninitialized memory usage.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio-ap: fix potential use of uninitialized apm_filtered bitmap\n\nThe DECLARE_BITMAP(apm_filtered, AP_DEVICES) macro allocates the bitmap\non the stack without zero-initializing it.\n\nIn vfio_ap_mdev_hot_plug_cfg(), the vfio_ap_mdev_filter_matrix() function\nis only called to initialize and populate apm_filtered if either\nfilter_adapters or filter_domains is true. If the hot plug configuration\nchange only adds control domains (meaning filter_cdoms is true, but\nfilter_adapters and filter_domains are both false),\nvfio_ap_mdev_filter_matrix() is bypassed.\n\nConsequently, apm_filtered is passed to reset_queues_for_apids() with\nuninitialized stack garbage. This can cause reset_queues_for_apids() to\ninterpret arbitrary stack garbage bits as valid APIDs to reset, potentially\nperforming unintended guest hardware queue resets.\n\nFix this by zero-initializing the apm_filtered bitmap at the beginning of\nvfio_ap_mdev_hot_plug_cfg() using bitmap_zero().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"s390/vfio-ap: fix potential use of uninitialized apm_filtered bitmap","id":"CVE-2026-93238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"arm64: mm: Fix the lockless page-table walk in show_pte()","id":"CVE-2026-93239"},"packages":[],"prev":{"headline":"LoongArch: Add DIRECT_MAP_PHYSMEM_END definition","id":"CVE-2026-93237"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker with high privileges can trigger unintended guest hardware queue resets in the Linux kernel s390/vfio-ap driver due to uninitialized memory usage.","url":"https://insights.sbomify.com/CVE-2026-93238/"}