Linux KernelOperating system · Linux
CVE-2026-53057
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Linux kernel's RISC-V IOMMU driver fails to perform required IOTINVAL (I/O TLB and context cache invalidations) after updating DDT (Device Directory Table) or PDT (Process Directory Table) entries. Without these invalidations, stale TLB entries may persist, causing devices to access incorrect memory translations. This violates the RISC-V IOMMU specification (Sections 6.3.1 and 6.3.2) and could lead to data corruption or security boundary bypasses.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 6.13, < 6.18.33>= 6.19, < 7.0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify RISC-V architectureCheck system architecture with 'uname -m' or 'cat /proc/cpuinfo' - look for 'riscv' or 'rv64'Affected if System is not running on RISC-V architecture (vulnerability only applies to RISC-V systems)
-
Check kernel version for patch statusRun 'uname -r' to get kernel version; compare against the version that includes the riscv_iommu_iodir_iotinval() fixAffected if Kernel version predates the patch that adds the required IOTINVAL calls (vulnerability is present in unpatched kernels)
-
Verify RISC-V IOMMU driver is enabledCheck kernel config for 'CONFIG_RISCV_IOMMU' via 'grep CONFIG_RISCV_IOMMU /boot/config-$(uname -r)' or check if 'riscv-iommu' module is loaded via 'lsmod | grep riscv_iommu'Affected if RISC-V IOMMU driver is compiled as built-in (y) or loaded as module (vulnerable code path exists)
-
Confirm IOMMU hardware is presentCheck for IOMMU hardware by examining 'dmesg' for 'riscv-iommu' messages, or check device tree '/proc/device-tree' for 'riscv,iommu' compatible nodesAffected if RISC-V IOMMU hardware is detected and initialized (the driver would be actively managing translations)
A RISC-V system with an unpatched kernel version, with the RISC-V IOMMU driver enabled and hardware present, is vulnerable to using stale translations due to missing IOTINVAL after DDT/PDT updates.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data6.18.337.0.10
Apply the kernel patch that adds the riscv_iommu_iodir_iotinval() function to perform mandatory TLB and context cache invalidations after DDT/PDT updates. This is a code-level fix requiring kernel update deployment.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53057 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data