Skip to main content

Linux Kernel CVE-2026-89959

| EUVDEUVD-2026-80559 HIGH
2026-09-16 Linux GHSA-8mfq-hrvh-mwqh
8.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Guest granted AP crypto passthrough on s390 host
  2. Delivery
    Admin unplugs a control domain from mdev
  3. Exploit
    Buggy bitmap_andnot fails to clear adm bit
  4. Execution
    Guest retains stale control-domain access
  5. Impact
    Guest issues revoked crypto control operations

Vulnerability Assessment

Exploitation Conditions

Requires an IBM Z / s390 host running the Linux kernel with KVM and the vfio-ap module actively passing AP (Adjunct Processor) crypto adapters and control domains through to a guest via a matrix mdev. The flawed path is reached only when a host administrator explicitly removes/unplugs a control domain from that mdev; the failure is that the removal does not propagate to the guest. LIMITING FACTORS: exploitation is confined to systems using s390 crypto passthrough (a rare deployment mode), the trigger is a privileged host reconfiguration action rather than remote input, and the resulting exposure is limited to retained crypto control-domain access rather than arbitrary code execution.

Impact

The vendor CVSS of 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) substantially overstates real-world risk for what is fundamentally a control-flow bug in host reconfiguration logic. The defect: vfio_ap_config_remove used bitmap_andnot instead of bitmap_and when clearing the matrix.adm bitmap, so control domains an administrator explicitly unplugs are NOT actually withdrawn from the running KVM guest - the guest retains stale access to AP crypto control domains it should no longer possess. This is an isolation/access-control failure, not a memory-corruption RCE, so the C:H/I:H/A:H triad is inflated: the practical impact is bounded (a guest can continue issuing administrative/control commands to crypto domains that were meant to be revoked). It is triggered by a legitimate host administrative action (removing a control domain from an mdev), so PR:L understates the privilege actually needed to reach the buggy path (host-side vfio-ap configuration = admin). There is NO KEV listing, NO public POC, and no EPSS signal in the input - consistent with a low-real-risk, niche s390 issue. No availability impact is evident from the description despite A:H being asserted. Net: this is a correctness/isolation fix for IBM Z crypto passthrough, not an urgent priority for most fleets.

Exploit ScenarioDerived

On an IBM Z / s390 host running KVM with vfio-ap crypto passthrough, an administrator removes (unplugs) a control domain from a guest's mdev, expecting the guest to lose the ability to issue administrative crypto commands to that domain. Because of the bitmap_andnot bug, the domain is never actually cleared from the guest's adm bitmap, so the guest silently retains control-domain access and can continue performing privileged crypto operations (e.g., domain management) it was supposed to be denied. No public exploit code is identified at the time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 16, 2026

The s390 vfio-ap mediated device (mdev) driver in the Linux kernel fails to actually revoke crypto control-domain access when a privileged host administrator unplugs a control domain from a matrix mdev: vfio_ap_mdev_cfg_remove clears the wrong bit set with bitmap_andnot instead of intersecting with bitmap_and on the mdev's adm bitmap. The practical result is that a KVM guest on IBM Z hardware configured for AP (Adjunct Processor) passthrough retains access to control domains the host intended to remove, a residual-access/state-desynchronization condition rather than remote code execution, reached only when a host admin performs an explicit control-domain removal (CVSS 3.1 AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; the vendor-supplied 8.8 score (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) materially overstates real-world risk given that exploitation is confined to the rare s390 crypto-passthrough deployment mode and requires a trusted privileged reconfiguration action.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 6.1.188, 6.6.157, 6.12.110, 6.18.51 or 7.2.5 and later (mainline fix present in 7.3-rc1) - or backport the relevant upstream commit from the references (e.g. git.kernel.org/stable/c/f7d66afc34bc6e833c8ebe56973afec35f473bc1, 2ff68bf414de167bc138e6e211ee1ad3ab3c5052, 4bffadde7fc49b00493fb78c6376f958998d4b8c), which restores correct bitmap_and semantics in vfio_ap_config_remove. Until a patched kernel is running, do not rely on control-domain unplug as a security boundary: because the stale adm bits persist in the live matrix mdev, force a full matrix re-initialization by unbinding and rebinding the vfio-ap mediated device (or removing and recreating the matrix mdev) after changing control-domain assignment - trade-off is disruption to the guest's AP crypto workload and typically guest downtime. Stopping the guest before unplugging control domains achieves the same clean state at the cost of an outage; fully disabling AP passthrough on the host removes the exposure entirely but sacrifices hardware crypto acceleration for guests. Because the trigger is a privileged host reconfiguration action (CVSS PR:H), tighten who may administer vfio-ap mdevs and audit guest control-domain usage for stale access; note this is containment, not a fix, and the authoritative guidance remains the vendor advisory at https://nvd.nist.gov/vuln/detail/CVE-2026-89959 and the linked kernel.org stable commits.

Affected VersionsENISA

Linux patch: 7.2.5
Linux eeb386aeb5b7c8d2dae6a3ba49255d8a97803182 <f7d66afc34bc6e833c8ebe56973afec35f473bc1
Linux eeb386aeb5b7c8d2dae6a3ba49255d8a97803182 <6b8a02e216f6b520cc029e43ddc83956605135d5
Linux eeb386aeb5b7c8d2dae6a3ba49255d8a97803182 <12871a4269f139221c9fde9ea3eb69c9228f59d4
Linux patch: 6.1.188
Linux patch: 6.12.110
Linux patch: 0
Linux eeb386aeb5b7c8d2dae6a3ba49255d8a97803182 <2ff68bf414de167bc138e6e211ee1ad3ab3c5052
Linux patch: 6.6.157
Linux patch: 6.18.51
Linux eeb386aeb5b7c8d2dae6a3ba49255d8a97803182 <4bffadde7fc49b00493fb78c6376f958998d4b8c
Linux eeb386aeb5b7c8d2dae6a3ba49255d8a97803182 <02e72909453dee2f8a09f78819f9a9cb902dfbdc
Linux 6.0
Linux patch: 7.3-rc1

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the vfio-ap driver in the Linux kernel, which exposes s390 Adjunct Processor (AP) crypto adapters and their control domains to KVM guests through a VFIO mediated device. Each mdev carries a "matrix" describing assignment, stored as bitmaps: apm (AP adapters), aqm (AP queues) and adm (control domains). The vulnerability is a bit-manipulation logic error in vfio_ap_config_remove, the code path used by vfio_ap_mdev_cfg_remove when an administrator unplugs a control domain: it used bitmap_andnot (which clears bits in the destination rather than computing the intended removal/intersection semantics) instead of bitmap_and, so the explicitly unplugged control domain bits are not actually removed from matrix_mdev->matrix.adm. The exposed state therefore stays visible to the guest, which is why the entry is tagged Information Disclosure. No CWE identifier was assigned in the source data; the root-cause class is an incorrect bitwise operation in host-side bitmap bookkeeping rather than memory corruption, so there is no overflow, use-after-free or privilege-escalation primitive - the flaw is limited to stale authorization state for AP crypto control domains. Affected CPE entries are cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* and a second linux:linux entry, i.e. mainline/stable kernel code carrying the vulnerable vfio-ap remove path.

Know when KVM gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 8.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 4.6 MEDIUM

Local s390 host with vfio-ap configured (AV:L), reached via a privileged admin reconfiguration (PR:H); stale control-domain access breaks guest isolation (S:C) with bounded confidentiality/integrity and no availability impact.

3.1 AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
SUSE 4.6 MEDIUM
AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
Red Hat 6.1 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 16, 2026 - 15:22 NVD
8.8 (HIGH)
Patch available
Sep 16, 2026 - 11:03 EUVD
CVE Published
Sep 16, 2026 - 10:32 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 16, 2026 - 10:32 cve.org
HIGH 8.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove

The vfio_ap_config_remove function uses the bitmap_andnot function to clear bits from the matrix_mdev->matrix.adm bitmap (specifies the control domains assigned to the mdev). This prevents the explicitly unplugged control domains from being removed the KVM guest. The bitmap_and function is used instead.

Executive ViewAI

Why It Matters

A flaw in the Linux kernel's s390 vfio-ap mediated device driver affects IBM Z hosts configured for AP passthrough, causing KVM guests to retain access to crypto control domains that a privileged host administrator intended to revoke. The practical impact is a residual-access and state-desynchronization condition limited to rare s390 crypto-passthrough deployments; no public exploit code exists and it is not in CISA KEV. Leadership should care because affected mainframe environments may have weakened crypto isolation until the vendor patch is applied.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
niche s390/IBM Z KVM vfio-ap crypto passthrough, minimal general footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in KVM

View all
CVE-2026-27211 CRITICAL
10.0 Feb 21

Arbitrary host file exfiltration from Cloud Hypervisor VMM versions 34.0-50.0. CVSS 10.0. Patch available.

CVE-2026-89930 CRITICAL
9.3 Sep 16

Incorrect handling of queued local TLB flushes in the Linux kernel's KVM nested-VMX (nVMX) implementation can leave stal

CVE-2026-89918 CRITICAL
9.3 Sep 16

Address-rollover bug in the Linux kernel's KVM/arm64 TLB-by-VA invalidation path causes the hypervisor to silently skip

CVE-2026-89916 CRITICAL
9.3 Sep 16

Race conditions in the arm64 KVM path that invalidates VNCR translations can leave a stale stage-1 TLB entry installed f

CVE-2026-89915 CRITICAL
9.3 Sep 16

Missed TLB invalidations in the arm64 KVM nested-virtualization path of the Linux kernel can leave stale translations fo

CVE-2026-89914 CRITICAL
9.3 Sep 16

Range-based TLB invalidation in the arm64 KVM hypervisor of the Linux kernel is computed against the wrong address range

CVE-2026-89913 HIGH
8.8 Sep 16

A use-after-free race in the arm64 KVM vGICv3 code path of the Linux kernel (vgic_v3_save_pending_tables) allows a local

CVE-2026-89957 HIGH
8.8 Sep 16

Stale hardware access to unplugged crypto resources in Linux KVM guests on IBM Z (s390) stems from a logic error in the

CVE-2026-89932 HIGH
8.8 Sep 16

Stale TLB entries can be reused by an L2 guest in the Linux kernel's KVM nested virtualization (nVMX) implementation on

CVE-2026-89929 HIGH
8.8 Sep 16

Linux kernel's KVM nested-VMX (nVMX) emulation can leave stale L2 guest TLB entries on a physical CPU, because KVM execu

CVE-2026-89908 HIGH
8.8 Sep 16

On LoongArch hosts running KVM, a memory-slot update that changes only flags (KVM_MR_FLAGS_ONLY, most notably toggling K

CVE-2026-89960 HIGH
8.8 Sep 16

A use-after-free (CWE-416) in the Linux kernel's s390/vfio-ap AP crypto passthrough driver allows a local attacker with

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy