// For flags

CVE-2024-26620

s390/vfio-ap: always filter entire AP matrix

Severity Score

"-"
*CVSS v-

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

0
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

Track
*SSVC
Descriptions

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

s390/vfio-ap: always filter entire AP matrix

The vfio_ap_mdev_filter_matrix function is called whenever a new adapter or
domain is assigned to the mdev. The purpose of the function is to update
the guest's AP configuration by filtering the matrix of adapters and
domains assigned to the mdev. When an adapter or domain is assigned, only
the APQNs associated with the APID of the new adapter or APQI of the new
domain are inspected. If an APQN does not reference a queue device bound to
the vfio_ap device driver, then it's APID will be filtered from the mdev's
matrix when updating the guest's AP configuration.

Inspecting only the APID of the new adapter or APQI of the new domain will
result in passing AP queues through to a guest that are not bound to the
vfio_ap device driver under certain circumstances. Consider the following:

guest's AP configuration (all also assigned to the mdev's matrix):
14.0004
14.0005
14.0006
16.0004
16.0005
16.0006

unassign domain 4
unbind queue 16.0005
assign domain 4

When domain 4 is re-assigned, since only domain 4 will be inspected, the
APQNs that will be examined will be:
14.0004
16.0004

Since both of those APQNs reference queue devices that are bound to the
vfio_ap device driver, nothing will get filtered from the mdev's matrix
when updating the guest's AP configuration. Consequently, queue 16.0005
will get passed through despite not being bound to the driver. This
violates the linux device model requirement that a guest shall only be
given access to devices bound to the device driver facilitating their
pass-through.

To resolve this problem, every adapter and domain assigned to the mdev will
be inspected when filtering the mdev's matrix.

En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: s390/vfio-ap: filtra siempre toda la matriz AP La función vfio_ap_mdev_filter_matrix se llama cada vez que se asigna un nuevo adaptador o dominio al mdev. El propósito de la función es actualizar la configuración del AP del invitado filtrando la matriz de adaptadores y dominios asignados al mdev. Cuando se asigna un adaptador o dominio, solo se inspeccionan los APQN asociados con el APID del nuevo adaptador o APQI del nuevo dominio. Si un APQN no hace referencia a un dispositivo de cola vinculado al controlador de dispositivo vfio_ap, entonces su APID se filtrará de la matriz de mdev al actualizar la configuración de AP del invitado. Inspeccionar solo el APID del nuevo adaptador o APQI del nuevo dominio dará como resultado que se pasen colas de AP a un invitado que no está vinculado al controlador de dispositivo vfio_ap en determinadas circunstancias. Considere lo siguiente: configuración de AP del invitado (todas también asignadas a la matriz de mdev): 14.0004 14.0005 14.0006 16.0004 16.0005 16.0006 desasignar dominio 4 desvincular cola 16.0005 asignar dominio 4 Cuando se reasigna el dominio 4, dado que solo se inspeccionará el dominio 4, los APQN que se examinará será: 14.0004 16.0004 Dado que ambos APQN hacen referencia a dispositivos de cola que están vinculados al controlador de dispositivo vfio_ap, no se filtrará nada de la matriz de mdev al actualizar la configuración de AP del invitado. En consecuencia, la cola 16.0005 pasará a pesar de no estar vinculada al conductor. Esto viola el requisito del modelo de dispositivo Linux de que a un invitado solo se le dará acceso a los dispositivos vinculados al controlador del dispositivo que facilita su paso. Para resolver este problema, cada adaptador y dominio asignado al mdev se inspeccionará al filtrar la matriz del mdev.

*Credits: N/A
CVSS Scores
Attack Vector
-
Attack Complexity
-
Privileges Required
-
User Interaction
-
Scope
-
Confidentiality
-
Integrity
-
Availability
-
* Common Vulnerability Scoring System
SSVC
  • Decision:Track
Exploitation
None
Automatable
No
Tech. Impact
Partial
* Organization's Worst-case Scenario
Timeline
  • 2024-02-19 CVE Reserved
  • 2024-02-29 CVE Published
  • 2024-03-01 EPSS Updated
  • 2024-08-02 CVE Updated
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
  • ---------- First Exploit
CWE
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Linux
Search vendor "Linux"
Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
>= 6.0 < 6.1.76
Search vendor "Linux" for product "Linux Kernel" and version " >= 6.0 < 6.1.76"
en
Affected
Linux
Search vendor "Linux"
Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
>= 6.0 < 6.6.15
Search vendor "Linux" for product "Linux Kernel" and version " >= 6.0 < 6.6.15"
en
Affected
Linux
Search vendor "Linux"
Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
>= 6.0 < 6.7.3
Search vendor "Linux" for product "Linux Kernel" and version " >= 6.0 < 6.7.3"
en
Affected
Linux
Search vendor "Linux"
Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
>= 6.0 < 6.8
Search vendor "Linux" for product "Linux Kernel" and version " >= 6.0 < 6.8"
en
Affected