FKIE_CVE-2026-74713

Vulnerability from fkie_nvd - Published: 2026-08-22 16:16 - Updated: 2026-10-16 20:17
Severity
7.1 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: vhost_iotlb: bound map allocation in add_range vhost_iotlb_add_range_ctx() only retires an old entry when the table has a non-zero limit, has exactly reached that limit and has VHOST_IOTLB_FLAG_RETIRE set. Non-retiring tables can keep allocating entries after reaching their configured limit. Existing vhost devices allocate their IOTLB with max_iotlb_entries from vhost.c, which defaults to 2048 and is tunable by module parameter. Use the caller-provided limit at the allocation point instead of adding a separate default in the common IOTLB helper, and reject non-positive values in vhost paths that can report an error. Other vhost IOTLB users should not create zero-limit tables when entries can be populated from userspace or guest-controlled requests. Add caller-side max_iotlb_entries parameters for mlx5 vDPA, VDUSE and vhost-vDPA. Reject non-positive VDUSE and vhost-vDPA values, and require at least two entries for vdpa_sim and mlx5 vDPA paths that install full-range mappings, since those mappings are split into two IOTLB entries. Handle full-range mappings in the common helper by checking that the IOTLB can hold both split entries before inserting the first half. This avoids returning an error after leaving a half mapping behind. When the table is full, keep the existing retire behavior for retiring tables and return -ENOSPC for non-retiring tables. Reuse the retired map node instead of freeing it and allocating a replacement, so a stream of IOTLB updates cannot keep forcing GFP_ATOMIC allocations after the table has reached its limit. If a zero-limit IOTLB still reaches the common helper, treat it as a configuration error and return -EINVAL. I found this bug myself, though the patch was written with AI assistance.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ae128dd19040ee06a4f8143c7ced4d18080d7a9a
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b57164cdddb46924ff9fa191b727ca097744de88
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/vdpa/mlx5/core/mlx5_vdpa.h",
            "drivers/vdpa/mlx5/core/mr.c",
            "drivers/vdpa/mlx5/core/resources.c",
            "drivers/vdpa/vdpa_sim/vdpa_sim.c",
            "drivers/vdpa/vdpa_user/iova_domain.c",
            "drivers/vhost/iotlb.c",
            "drivers/vhost/vdpa.c",
            "drivers/vhost/vhost.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "b57164cdddb46924ff9fa191b727ca097744de88",
              "status": "affected",
              "version": "0bbe30668d89ec8a309f28ced6d092c90fb23e8c",
              "versionType": "git"
            },
            {
              "lessThan": "ae128dd19040ee06a4f8143c7ced4d18080d7a9a",
              "status": "affected",
              "version": "0bbe30668d89ec8a309f28ced6d092c90fb23e8c",
              "versionType": "git"
            },
            {
              "lessThan": "1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94",
              "status": "affected",
              "version": "0bbe30668d89ec8a309f28ced6d092c90fb23e8c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/vdpa/mlx5/core/mlx5_vdpa.h",
            "drivers/vdpa/mlx5/core/mr.c",
            "drivers/vdpa/mlx5/core/resources.c",
            "drivers/vdpa/vdpa_sim/vdpa_sim.c",
            "drivers/vdpa/vdpa_user/iova_domain.c",
            "drivers/vhost/iotlb.c",
            "drivers/vhost/vdpa.c",
            "drivers/vhost/vhost.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.7"
            },
            {
              "lessThan": "5.7",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nvhost_iotlb: bound map allocation in add_range\n\nvhost_iotlb_add_range_ctx() only retires an old entry when the table\nhas a non-zero limit, has exactly reached that limit and has\nVHOST_IOTLB_FLAG_RETIRE set. Non-retiring tables can keep allocating\nentries after reaching their configured limit.\n\nExisting vhost devices allocate their IOTLB with max_iotlb_entries from\nvhost.c, which defaults to 2048 and is tunable by module parameter. Use\nthe caller-provided limit at the allocation point instead of adding a\nseparate default in the common IOTLB helper, and reject non-positive\nvalues in vhost paths that can report an error.\n\nOther vhost IOTLB users should not create zero-limit tables when entries\ncan be populated from userspace or guest-controlled requests. Add\ncaller-side max_iotlb_entries parameters for mlx5 vDPA, VDUSE and\nvhost-vDPA. Reject non-positive VDUSE and vhost-vDPA values, and require\nat least two entries for vdpa_sim and mlx5 vDPA paths that install\nfull-range mappings, since those mappings are split into two IOTLB\nentries.\n\nHandle full-range mappings in the common helper by checking that the\nIOTLB can hold both split entries before inserting the first half. This\navoids returning an error after leaving a half mapping behind.\n\nWhen the table is full, keep the existing retire behavior for retiring\ntables and return -ENOSPC for non-retiring tables. Reuse the retired map\nnode instead of freeing it and allocating a replacement, so a stream of\nIOTLB updates cannot keep forcing GFP_ATOMIC allocations after the table\nhas reached its limit. If a zero-limit IOTLB still reaches the common\nhelper, treat it as a configuration error and return -EINVAL.\n\nI found this bug myself, though the patch was written with AI assistance."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nvhost_iotlb: asignaci\u00f3n de mapa limitada en add_range\n\nvhost_iotlb_add_range_ctx() solo retira una entrada antigua cuando la tabla tiene un l\u00edmite no nulo, ha alcanzado exactamente ese l\u00edmite y tiene VHOST_IOTLB_FLAG_RETIRE establecido. Las tablas que no retiran pueden seguir asignando entradas despu\u00e9s de alcanzar su l\u00edmite configurado.\n\nLos dispositivos vhost existentes asignan su IOTLB con max_iotlb_entries de vhost.c, que por defecto es 2048 y es configurable mediante un par\u00e1metro de m\u00f3dulo. Utilice el l\u00edmite proporcionado por el llamador en el punto de asignaci\u00f3n en lugar de a\u00f1adir un valor predeterminado separado en el asistente IOTLB com\u00fan, y rechace los valores no positivos en las rutas vhost que pueden informar un error.\n\nOtros usuarios de IOTLB de vhost no deben crear tablas de l\u00edmite cero cuando las entradas pueden ser pobladas desde el espacio de usuario o solicitudes controladas por el invitado. A\u00f1ada par\u00e1metros max_iotlb_entries del lado del llamador para mlx5 vDPA, VDUSE y vhost-vDPA. Rechace los valores no positivos de VDUSE y vhost-vDPA, y requiera al menos dos entradas para las rutas vdpa_sim y mlx5 vDPA que instalan mapeos de rango completo, ya que esos mapeos se dividen en dos entradas IOTLB.\n\nManeje los mapeos de rango completo en el asistente com\u00fan verificando que el IOTLB puede contener ambas entradas divididas antes de insertar la primera mitad. Esto evita devolver un error despu\u00e9s de dejar un mapeo a medias.\n\nCuando la tabla est\u00e1 llena, mantenga el comportamiento de retiro existente para las tablas que retiran y devuelva -ENOSPC para las tablas que no retiran. Reutilice el nodo de mapa retirado en lugar de liberarlo y asignar un reemplazo, para que un flujo de actualizaciones de IOTLB no pueda seguir forzando asignaciones GFP_ATOMIC despu\u00e9s de que la tabla haya alcanzado su l\u00edmite. Si un IOTLB de l\u00edmite cero a\u00fan llega al asistente com\u00fan, tr\u00e1telo como un error de configuraci\u00f3n y devuelva -EINVAL.\n\nEncontr\u00e9 este error yo mismo, aunque el parche fue escrito con asistencia de IA."
    }
  ],
  "id": "CVE-2026-74713",
  "lastModified": "2026-10-16T20:17:53.887",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 7.1,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.5,
        "impactScore": 4.0,
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-74713",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-10-16T19:15:21.643384Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-08-22T16:16:46.063",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/ae128dd19040ee06a4f8143c7ced4d18080d7a9a"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/b57164cdddb46924ff9fa191b727ca097744de88"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.