{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89957 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89957 is a high-severity vulnerability in Linux, published on 16 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-89957 and fix it if it is affected.\n\nWhat it is: CVE-2026-89957 is a high-severity vulnerability in Linux, published on 16 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-89957 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-89957/ (Markdown: https://insights.sbomify.com/CVE-2026-89957/index.md)","id":"CVE-2026-89957","markdown":"https://insights.sbomify.com/CVE-2026-89957/index.md","name":"CVE-2026-89957","record":{"aliases":["AZL-101433","BELL-CVE-2026-89957","DEBIAN-CVE-2026-89957","GHSA-pgcj-5wj3-jcmr","UBUNTU-CVE-2026-89957"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A logic error in the Linux kernel vfio-ap driver allows KVM guests to retain stale access to unplugged AP devices, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio-ap: Fix hot-unplug skipped when last AP adapter or domain removed\n\nThe vfio_ap_mdev_hot_unplug_cfg() function uses the return value of\nbitmap_andnot() to determine whether the guest APCB needs to be updated.\nHowever, bitmap_andnot() returns false when the resulting destination\nbitmap is empty. This means that if the only adapter, domain or control\ndomain assigned to an mdev is removed from the host's AP configuration,\nthe bit is correctly cleared from the shadow APCB, but bitmap_andnot()\nreturns false because the result is an empty bitmap. Consequently,\ndo_hotplug remains 0 and vfio_ap_mdev_update_guest_apcb() is never called,\nleaving the KVM guest with stale hardware access to the unplugged AP\ndevices.\n\nFix this by replacing the bitmap_andnot() return value check with\nbitmap_intersects() to determine whether the shadow APCB actually\noverlaps with the removal mask. If there is an intersection, call\nbitmap_andnot() solely for its side effect of clearing the bits, then\nunconditionally set do_hotplug to trigger the guest APCB update.","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 hot-unplug skipped when last AP adapter or domain removed","id":"CVE-2026-89957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"s390/vfio-ap: Fix dereference matrix_mdev-\u003ekvm without checking for NULL","id":"CVE-2026-89958"},"packages":[],"prev":{"headline":"s390/vfio-ap: Fix missing lock required to access list of ap_matrix_mdev objects","id":"CVE-2026-89956"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A logic error in the Linux kernel vfio-ap driver allows KVM guests to retain stale access to unplugged AP devices, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-89957/"}