CVE-2026-53057 (GCVE-0-2026-53057)
Vulnerability from cvelistv5
Published
2026-06-24 16:30
Modified
2026-08-05 12:33
Summary
In the Linux kernel, the following vulnerability has been resolved: iommu/riscv: Add IOTINVAL after updating DDT/PDT entries Add riscv_iommu_iodir_iotinval() to perform required TLB and context cache invalidations after updating DDT or PDT entries, as mandated by the RISC-V IOMMU specification (Section 6.3.1 and 6.3.2).
Impacted products
Vendor Product Version
Linux Linux Version: 488ffbf181718b9ad8c1838cb249d60973e78eda
Version: 488ffbf181718b9ad8c1838cb249d60973e78eda
Version: 488ffbf181718b9ad8c1838cb249d60973e78eda
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/riscv/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "3f917d9bff68600f77561900f3145bd4706dc840",
              "status": "affected",
              "version": "488ffbf181718b9ad8c1838cb249d60973e78eda",
              "versionType": "git"
            },
            {
              "lessThan": "d99d1c13faa793ff1abab0d20ab6473c838081b3",
              "status": "affected",
              "version": "488ffbf181718b9ad8c1838cb249d60973e78eda",
              "versionType": "git"
            },
            {
              "lessThan": "f5c262b544975e067ea265fc7403aefbbea8563e",
              "status": "affected",
              "version": "488ffbf181718b9ad8c1838cb249d60973e78eda",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/riscv/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.13"
            },
            {
              "lessThan": "6.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.33",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.33",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.10",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/riscv: Add IOTINVAL after updating DDT/PDT entries\n\nAdd riscv_iommu_iodir_iotinval() to perform required TLB and context cache\ninvalidations after updating DDT or PDT entries, as mandated by the RISC-V\nIOMMU specification (Section 6.3.1 and 6.3.2)."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerable RISC-V IOMMU path is reached through local device/IOMMU management flows such as VFIO/iommufd domain attach, detach, or replacement for DMA-capable devices. It is not directly reachable from network packets.\nAC:L - An attacker controlling an assigned DMA-capable device can prepopulate translation caches and trigger domain changes without needing to win an uncontrollable race. The bug is a missing required invalidation after DDT/PDT updates.\nPR:L - Exploitation requires local access to a DMA-capable device or delegated VFIO/iommufd device ownership, which is commonly granted to non-root users or guest workloads. It does not require real init-namespace root once that device access exists.\nUI:N - No separate victim action is required after the attacker has device access. The attacker can trigger DMA and domain transitions directly through the local device management path.\nS:C - This is an IOMMU/DMA isolation failure, so stale translations can cross the intended device, guest, or host memory protection boundary. Kernel guidance treats IOMMU/DMA boundary bypass as scope changed.\nC:H - Stale DDT/PDT-derived translations can allow a device to DMA-read memory belonging to a previous or different protection domain. In the severe reasonable VFIO or passthrough scenario, this can expose arbitrary host or other-guest memory.\nI:H - The same stale translations can permit DMA writes outside the attacker\u0027s assigned domain. That can corrupt host or other-guest memory and potentially alter privileged state.\nA:H - Unauthorized DMA writes or stale-domain DMA after blocking/detach can corrupt critical memory and crash or hang the host or victim workload. Repeated triggering is feasible through local device control."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:33:00.472Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/3f917d9bff68600f77561900f3145bd4706dc840"
        },
        {
          "url": "https://git.kernel.org/stable/c/d99d1c13faa793ff1abab0d20ab6473c838081b3"
        },
        {
          "url": "https://git.kernel.org/stable/c/f5c262b544975e067ea265fc7403aefbbea8563e"
        }
      ],
      "title": "iommu/riscv: Add IOTINVAL after updating DDT/PDT entries",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-53057",
    "datePublished": "2026-06-24T16:30:02.571Z",
    "dateReserved": "2026-06-09T07:44:35.381Z",
    "dateUpdated": "2026-08-05T12:33:00.472Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…