GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2024-26620 (GCVE-0-2024-26620)

Vulnerability from cvelistv5 – Published: 2024-02-29 15:52 – Updated: 2026-08-05 11:26
VLAI
Title
s390/vfio-ap: always filter entire AP matrix
Summary
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.
Severity
8.2 (High)
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2024-06-21 16:17 UTC
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 48cae940c31d2407d860d87c41d5f9871c0521db , < d6b8d034b576f406af920a7bee81606c027b24c6 (git)
Affected: 48cae940c31d2407d860d87c41d5f9871c0521db , < c69d821197611678533fb3eb784fc823b921349a (git)
Affected: 48cae940c31d2407d860d87c41d5f9871c0521db , < cdd134d56138302976685e6c7bc4755450b3880e (git)
Affected: 48cae940c31d2407d860d87c41d5f9871c0521db , < 850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11 (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.0
Unaffected: 0 , < 6.0 (semver)
Unaffected: 6.1.76 , ≤ 6.1.* (semver)
Unaffected: 6.6.15 , ≤ 6.6.* (semver)
Unaffected: 6.7.3 , ≤ 6.7.* (semver)
Unaffected: 6.8 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-26620",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-06-21T16:17:50.706857Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-21T16:18:01.425Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T00:07:19.626Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/s390/crypto/vfio_ap_ops.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d6b8d034b576f406af920a7bee81606c027b24c6",
              "status": "affected",
              "version": "48cae940c31d2407d860d87c41d5f9871c0521db",
              "versionType": "git"
            },
            {
              "lessThan": "c69d821197611678533fb3eb784fc823b921349a",
              "status": "affected",
              "version": "48cae940c31d2407d860d87c41d5f9871c0521db",
              "versionType": "git"
            },
            {
              "lessThan": "cdd134d56138302976685e6c7bc4755450b3880e",
              "status": "affected",
              "version": "48cae940c31d2407d860d87c41d5f9871c0521db",
              "versionType": "git"
            },
            {
              "lessThan": "850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11",
              "status": "affected",
              "version": "48cae940c31d2407d860d87c41d5f9871c0521db",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/s390/crypto/vfio_ap_ops.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.0"
            },
            {
              "lessThan": "6.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.76",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.15",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.7.*",
              "status": "unaffected",
              "version": "6.7.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.8",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.76",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.15",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.7.3",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.8",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio-ap: always filter entire AP matrix\n\nThe vfio_ap_mdev_filter_matrix function is called whenever a new adapter or\ndomain is assigned to the mdev. The purpose of the function is to update\nthe guest\u0027s AP configuration by filtering the matrix of adapters and\ndomains assigned to the mdev. When an adapter or domain is assigned, only\nthe APQNs associated with the APID of the new adapter or APQI of the new\ndomain are inspected. If an APQN does not reference a queue device bound to\nthe vfio_ap device driver, then it\u0027s APID will be filtered from the mdev\u0027s\nmatrix when updating the guest\u0027s AP configuration.\n\nInspecting only the APID of the new adapter or APQI of the new domain will\nresult in passing AP queues through to a guest that are not bound to the\nvfio_ap device driver under certain circumstances. Consider the following:\n\nguest\u0027s AP configuration (all also assigned to the mdev\u0027s matrix):\n14.0004\n14.0005\n14.0006\n16.0004\n16.0005\n16.0006\n\nunassign domain 4\nunbind queue 16.0005\nassign domain 4\n\nWhen domain 4 is re-assigned, since only domain 4 will be inspected, the\nAPQNs that will be examined will be:\n14.0004\n16.0004\n\nSince both of those APQNs reference queue devices that are bound to the\nvfio_ap device driver, nothing will get filtered from the mdev\u0027s matrix\nwhen updating the guest\u0027s AP configuration. Consequently, queue 16.0005\nwill get passed through despite not being bound to the driver. This\nviolates the linux device model requirement that a guest shall only be\ngiven access to devices bound to the device driver facilitating their\npass-through.\n\nTo resolve this problem, every adapter and domain assigned to the mdev will\nbe inspected when filtering the mdev\u0027s matrix."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.2,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerability is triggered through local host interfaces \u2014 writes to the mdev\u0027s `assign_adapter`/`assign_domain` sysfs attributes and AP queue driver bind/unbind on the s390 host, or a host AP configuration change handled by `vfio_ap_mdev_hot_plug_cfg()`. There is no network-reachable path into `vfio_ap_mdev_filter_matrix()`.\nAC:L - The condition is fully deterministic and reproducible \u2014 the documented unassign-domain / unbind-queue / reassign-domain sequence reliably restores an unbound APQN into the guest\u0027s shadow APCB every time, with no race, timing window, or memory-layout dependency.\nPR:H - Both `assign_adapter_store` and `assign_domain_store` are `DEVICE_ATTR_WO` (mode 0200) on the vfio_ap matrix mdev, and unbinding a queue from the driver requires writing `/sys/bus/ap/drivers/vfio_ap/unbind`; these are real-root host administrative operations that cannot be obtained through user namespaces.\nUI:N - Once the assignment sequence is performed, `vfio_ap_mdev_update_guest_apcb()` immediately pushes the over-permissive APCB to the running guest via `kvm_arch_crypto_set_masks()`. No separate victim action is needed for the unauthorized queue to become live.\nS:C - The bug in the host\u0027s vfio-ap passthrough logic grants a KVM guest direct millicode-enforced hardware access to an AP queue outside the resources delegated to it \u2014 crossing the VM/device-passthrough isolation boundary into the host\u0027s (or another consumer\u0027s) security authority, analogous to an IOMMU/DMA boundary bypass.\nC:H - NQAP/DQAP are not host-intercepted, so the guest can dequeue replies from a queue still owned by the host zcrypt stack, exposing host cryptographic request/response data and key material; the sibling fix in the same series explicitly cites preventing \"leaking crypto data\" to a different guest or device driver.\nI:H - The guest can enqueue arbitrary AP requests and issue queue-state-changing commands to a physical adapter/domain that the host believes it exclusively controls, corrupting host crypto operations and altering hardware queue state outside the guest\u0027s authorized configuration.\nA:H - The guest can issue PQAP(ZAPQ) resets or flood the shared queue, disrupting host crypto services that depend on it (pkey, secure-key LUKS, openCryptoki); because the queue is not bound to vfio_ap it also escapes the driver\u0027s reset/cleanup accounting, leaving the hardware in an inconsistent state."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:26:18.311Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6"
        },
        {
          "url": "https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a"
        },
        {
          "url": "https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e"
        },
        {
          "url": "https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11"
        }
      ],
      "title": "s390/vfio-ap: always filter entire AP matrix",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-26620",
    "datePublished": "2024-02-29T15:52:21.743Z",
    "dateReserved": "2024-02-19T14:20:24.132Z",
    "dateUpdated": "2026-08-05T11:26:18.311Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-26620",
      "date": "2026-09-15",
      "epss": "0.00627",
      "percentile": "0.48236"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ns390/vfio-ap: always filter entire AP matrix\\n\\nThe vfio_ap_mdev_filter_matrix function is called whenever a new adapter or\\ndomain is assigned to the mdev. The purpose of the function is to update\\nthe guest\u0027s AP configuration by filtering the matrix of adapters and\\ndomains assigned to the mdev. When an adapter or domain is assigned, only\\nthe APQNs associated with the APID of the new adapter or APQI of the new\\ndomain are inspected. If an APQN does not reference a queue device bound to\\nthe vfio_ap device driver, then it\u0027s APID will be filtered from the mdev\u0027s\\nmatrix when updating the guest\u0027s AP configuration.\\n\\nInspecting only the APID of the new adapter or APQI of the new domain will\\nresult in passing AP queues through to a guest that are not bound to the\\nvfio_ap device driver under certain circumstances. Consider the following:\\n\\nguest\u0027s AP configuration (all also assigned to the mdev\u0027s matrix):\\n14.0004\\n14.0005\\n14.0006\\n16.0004\\n16.0005\\n16.0006\\n\\nunassign domain 4\\nunbind queue 16.0005\\nassign domain 4\\n\\nWhen domain 4 is re-assigned, since only domain 4 will be inspected, the\\nAPQNs that will be examined will be:\\n14.0004\\n16.0004\\n\\nSince both of those APQNs reference queue devices that are bound to the\\nvfio_ap device driver, nothing will get filtered from the mdev\u0027s matrix\\nwhen updating the guest\u0027s AP configuration. Consequently, queue 16.0005\\nwill get passed through despite not being bound to the driver. This\\nviolates the linux device model requirement that a guest shall only be\\ngiven access to devices bound to the device driver facilitating their\\npass-through.\\n\\nTo resolve this problem, every adapter and domain assigned to the mdev will\\nbe inspected when filtering the mdev\u0027s matrix.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: s390/vfio-ap: filtra siempre toda la matriz AP La funci\\u00f3n vfio_ap_mdev_filter_matrix se llama cada vez que se asigna un nuevo adaptador o dominio al mdev. El prop\\u00f3sito de la funci\\u00f3n es actualizar la configuraci\\u00f3n 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\\u00e1 de la matriz de mdev al actualizar la configuraci\\u00f3n de AP del invitado. Inspeccionar solo el APID del nuevo adaptador o APQI del nuevo dominio dar\\u00e1 como resultado que se pasen colas de AP a un invitado que no est\\u00e1 vinculado al controlador de dispositivo vfio_ap en determinadas circunstancias. Considere lo siguiente: configuraci\\u00f3n de AP del invitado (todas tambi\\u00e9n 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\\u00e1 el dominio 4, los APQN que se examinar\\u00e1 ser\\u00e1: 14.0004 16.0004 Dado que ambos APQN hacen referencia a dispositivos de cola que est\\u00e1n vinculados al controlador de dispositivo vfio_ap, no se filtrar\\u00e1 nada de la matriz de mdev al actualizar la configuraci\\u00f3n de AP del invitado. En consecuencia, la cola 16.0005 pasar\\u00e1 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\\u00e1 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\\u00e1 al filtrar la matriz del mdev.\"}]",
      "id": "CVE-2024-26620",
      "lastModified": "2024-11-21T09:02:42.407",
      "published": "2024-03-11T18:15:19.613",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-26620\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-03-11T18:15:19.613\",\"lastModified\":\"2026-08-04T11:16:49.080\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ns390/vfio-ap: always filter entire AP matrix\\n\\nThe vfio_ap_mdev_filter_matrix function is called whenever a new adapter or\\ndomain is assigned to the mdev. The purpose of the function is to update\\nthe guest\u0027s AP configuration by filtering the matrix of adapters and\\ndomains assigned to the mdev. When an adapter or domain is assigned, only\\nthe APQNs associated with the APID of the new adapter or APQI of the new\\ndomain are inspected. If an APQN does not reference a queue device bound to\\nthe vfio_ap device driver, then it\u0027s APID will be filtered from the mdev\u0027s\\nmatrix when updating the guest\u0027s AP configuration.\\n\\nInspecting only the APID of the new adapter or APQI of the new domain will\\nresult in passing AP queues through to a guest that are not bound to the\\nvfio_ap device driver under certain circumstances. Consider the following:\\n\\nguest\u0027s AP configuration (all also assigned to the mdev\u0027s matrix):\\n14.0004\\n14.0005\\n14.0006\\n16.0004\\n16.0005\\n16.0006\\n\\nunassign domain 4\\nunbind queue 16.0005\\nassign domain 4\\n\\nWhen domain 4 is re-assigned, since only domain 4 will be inspected, the\\nAPQNs that will be examined will be:\\n14.0004\\n16.0004\\n\\nSince both of those APQNs reference queue devices that are bound to the\\nvfio_ap device driver, nothing will get filtered from the mdev\u0027s matrix\\nwhen updating the guest\u0027s AP configuration. Consequently, queue 16.0005\\nwill get passed through despite not being bound to the driver. This\\nviolates the linux device model requirement that a guest shall only be\\ngiven access to devices bound to the device driver facilitating their\\npass-through.\\n\\nTo resolve this problem, every adapter and domain assigned to the mdev will\\nbe inspected when filtering the mdev\u0027s matrix.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: s390/vfio-ap: filtra siempre toda la matriz AP La funci\u00f3n vfio_ap_mdev_filter_matrix se llama cada vez que se asigna un nuevo adaptador o dominio al mdev. El prop\u00f3sito de la funci\u00f3n es actualizar la configuraci\u00f3n 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\u00e1 de la matriz de mdev al actualizar la configuraci\u00f3n de AP del invitado. Inspeccionar solo el APID del nuevo adaptador o APQI del nuevo dominio dar\u00e1 como resultado que se pasen colas de AP a un invitado que no est\u00e1 vinculado al controlador de dispositivo vfio_ap en determinadas circunstancias. Considere lo siguiente: configuraci\u00f3n de AP del invitado (todas tambi\u00e9n 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\u00e1 el dominio 4, los APQN que se examinar\u00e1 ser\u00e1: 14.0004 16.0004 Dado que ambos APQN hacen referencia a dispositivos de cola que est\u00e1n vinculados al controlador de dispositivo vfio_ap, no se filtrar\u00e1 nada de la matriz de mdev al actualizar la configuraci\u00f3n de AP del invitado. En consecuencia, la cola 16.0005 pasar\u00e1 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\u00e1 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\u00e1 al filtrar la matriz del mdev.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/s390/crypto/vfio_ap_ops.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"48cae940c31d2407d860d87c41d5f9871c0521db\",\"lessThan\":\"d6b8d034b576f406af920a7bee81606c027b24c6\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"48cae940c31d2407d860d87c41d5f9871c0521db\",\"lessThan\":\"c69d821197611678533fb3eb784fc823b921349a\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"48cae940c31d2407d860d87c41d5f9871c0521db\",\"lessThan\":\"cdd134d56138302976685e6c7bc4755450b3880e\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"48cae940c31d2407d860d87c41d5f9871c0521db\",\"lessThan\":\"850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/s390/crypto/vfio_ap_ops.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.0\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.0\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.76\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.15\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.7.3\",\"lessThanOrEqual\":\"6.7.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.8\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H\",\"baseScore\":8.2,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"HIGH\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.5,\"impactScore\":6.0},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2024-06-21T16:17:50.706857Z\",\"id\":\"CVE-2024-26620\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-787\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.0\",\"versionEndExcluding\":\"6.1.76\",\"matchCriteriaId\":\"F0D771C0-5574-4035-8FBB-634A9C9CBA35\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.15\",\"matchCriteriaId\":\"87C718CB-AE3D-4B07-B4D9-BFF64183C468\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.7.3\",\"matchCriteriaId\":\"58FD5308-148A-40D3-B36A-0CA6B434A8BF\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Mailing List\",\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Mailing List\",\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Mailing List\",\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Mailing List\",\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-08-04T22:52:22+00:00",
      "cve": "CVE-2024-26620",
      "id": "CVE-2024-26620",
      "initial_release_date": "2024-02-29T00:00:00+00:00",
      "product_status:known_not_affected": "198",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: s390/vfio-ap: always filter entire AP matrix",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-26620.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "important",
      "current_release_date": "2026-09-02T01:35:36Z",
      "cve": "CVE-2024-26620",
      "id": "CVE-2024-26620",
      "initial_release_date": "2024-03-13T04:22:11Z",
      "product_status:known_affected": "305",
      "product_status:known_not_affected": "321",
      "product_status:recommended": "528",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-26620",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-26620.json",
      "version": "61"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T00:07:19.626Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-26620\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-06-21T16:17:50.706857Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-06-21T16:17:56.258Z\"}}], \"cna\": {\"title\": \"s390/vfio-ap: always filter entire AP matrix\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 8.2, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The vulnerability is triggered through local host interfaces \\u2014 writes to the mdev\u0027s `assign_adapter`/`assign_domain` sysfs attributes and AP queue driver bind/unbind on the s390 host, or a host AP configuration change handled by `vfio_ap_mdev_hot_plug_cfg()`. There is no network-reachable path into `vfio_ap_mdev_filter_matrix()`.\\nAC:L - The condition is fully deterministic and reproducible \\u2014 the documented unassign-domain / unbind-queue / reassign-domain sequence reliably restores an unbound APQN into the guest\u0027s shadow APCB every time, with no race, timing window, or memory-layout dependency.\\nPR:H - Both `assign_adapter_store` and `assign_domain_store` are `DEVICE_ATTR_WO` (mode 0200) on the vfio_ap matrix mdev, and unbinding a queue from the driver requires writing `/sys/bus/ap/drivers/vfio_ap/unbind`; these are real-root host administrative operations that cannot be obtained through user namespaces.\\nUI:N - Once the assignment sequence is performed, `vfio_ap_mdev_update_guest_apcb()` immediately pushes the over-permissive APCB to the running guest via `kvm_arch_crypto_set_masks()`. No separate victim action is needed for the unauthorized queue to become live.\\nS:C - The bug in the host\u0027s vfio-ap passthrough logic grants a KVM guest direct millicode-enforced hardware access to an AP queue outside the resources delegated to it \\u2014 crossing the VM/device-passthrough isolation boundary into the host\u0027s (or another consumer\u0027s) security authority, analogous to an IOMMU/DMA boundary bypass.\\nC:H - NQAP/DQAP are not host-intercepted, so the guest can dequeue replies from a queue still owned by the host zcrypt stack, exposing host cryptographic request/response data and key material; the sibling fix in the same series explicitly cites preventing \\\"leaking crypto data\\\" to a different guest or device driver.\\nI:H - The guest can enqueue arbitrary AP requests and issue queue-state-changing commands to a physical adapter/domain that the host believes it exclusively controls, corrupting host crypto operations and altering hardware queue state outside the guest\u0027s authorized configuration.\\nA:H - The guest can issue PQAP(ZAPQ) resets or flood the shared queue, disrupting host crypto services that depend on it (pkey, secure-key LUKS, openCryptoki); because the queue is not bound to vfio_ap it also escapes the driver\u0027s reset/cleanup accounting, leaving the hardware in an inconsistent state.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"48cae940c31d2407d860d87c41d5f9871c0521db\", \"lessThan\": \"d6b8d034b576f406af920a7bee81606c027b24c6\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"48cae940c31d2407d860d87c41d5f9871c0521db\", \"lessThan\": \"c69d821197611678533fb3eb784fc823b921349a\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"48cae940c31d2407d860d87c41d5f9871c0521db\", \"lessThan\": \"cdd134d56138302976685e6c7bc4755450b3880e\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"48cae940c31d2407d860d87c41d5f9871c0521db\", \"lessThan\": \"850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/s390/crypto/vfio_ap_ops.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.0\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.0\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.1.76\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.15\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.7.3\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.7.*\"}, {\"status\": \"unaffected\", \"version\": \"6.8\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/s390/crypto/vfio_ap_ops.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/d6b8d034b576f406af920a7bee81606c027b24c6\"}, {\"url\": \"https://git.kernel.org/stable/c/c69d821197611678533fb3eb784fc823b921349a\"}, {\"url\": \"https://git.kernel.org/stable/c/cdd134d56138302976685e6c7bc4755450b3880e\"}, {\"url\": \"https://git.kernel.org/stable/c/850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ns390/vfio-ap: always filter entire AP matrix\\n\\nThe vfio_ap_mdev_filter_matrix function is called whenever a new adapter or\\ndomain is assigned to the mdev. The purpose of the function is to update\\nthe guest\u0027s AP configuration by filtering the matrix of adapters and\\ndomains assigned to the mdev. When an adapter or domain is assigned, only\\nthe APQNs associated with the APID of the new adapter or APQI of the new\\ndomain are inspected. If an APQN does not reference a queue device bound to\\nthe vfio_ap device driver, then it\u0027s APID will be filtered from the mdev\u0027s\\nmatrix when updating the guest\u0027s AP configuration.\\n\\nInspecting only the APID of the new adapter or APQI of the new domain will\\nresult in passing AP queues through to a guest that are not bound to the\\nvfio_ap device driver under certain circumstances. Consider the following:\\n\\nguest\u0027s AP configuration (all also assigned to the mdev\u0027s matrix):\\n14.0004\\n14.0005\\n14.0006\\n16.0004\\n16.0005\\n16.0006\\n\\nunassign domain 4\\nunbind queue 16.0005\\nassign domain 4\\n\\nWhen domain 4 is re-assigned, since only domain 4 will be inspected, the\\nAPQNs that will be examined will be:\\n14.0004\\n16.0004\\n\\nSince both of those APQNs reference queue devices that are bound to the\\nvfio_ap device driver, nothing will get filtered from the mdev\u0027s matrix\\nwhen updating the guest\u0027s AP configuration. Consequently, queue 16.0005\\nwill get passed through despite not being bound to the driver. This\\nviolates the linux device model requirement that a guest shall only be\\ngiven access to devices bound to the device driver facilitating their\\npass-through.\\n\\nTo resolve this problem, every adapter and domain assigned to the mdev will\\nbe inspected when filtering the mdev\u0027s matrix.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.76\", \"versionStartIncluding\": \"6.0\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.15\", \"versionStartIncluding\": \"6.0\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.7.3\", \"versionStartIncluding\": \"6.0\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.8\", \"versionStartIncluding\": \"6.0\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:26:18.311Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-26620\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:26:18.311Z\", \"dateReserved\": \"2024-02-19T14:20:24.132Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-02-29T15:52:21.743Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.