Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93205iommu/arm-smmu-v3: Manage teardown with devm

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3: Manage teardown with devm arm_smmu_device_remove() manually frees the IOPF queue, destroys the vmid_map and disables the device, while the IRQs and queues are devm managed. devm unwinds only after remove() returns, so the cleanup runs in the wrong order. The IOPF queue is freed before the event-queue IRQ whose handler uses it. Manage all of it with devm so the unwind order is correct. Free the IOPF queue and vmid_map via devm actions, and disable the device from one registered after arm_smmu_device_reset(). This is also a prerequisite for fixing a Tegra241 CMDQV CMD_SYNC use-after-free in the subsequent patch.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 36 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 395ad89d11fd93f79a6b942e91fc409807a63c4b – < 041b5e2a2a31c62049af30c5716099eebab86cb8
    • affected 395ad89d11fd93f79a6b942e91fc409807a63c4b – < 64b1a9384db9cabf1bde378a2d5c1923fd67ea0d
    • affected 395ad89d11fd93f79a6b942e91fc409807a63c4b – < 981686f4137760a16a03c5193f11d85133533f93
    • affected 395ad89d11fd93f79a6b942e91fc409807a63c4b – < 2235eafda9b3df9295efd0593cd4a8977440c3f6
    • affected 395ad89d11fd93f79a6b942e91fc409807a63c4b – < 78fd5a2d65f3546cb4285f8e52f445baecbd00e0
    • affected 395ad89d11fd93f79a6b942e91fc409807a63c4b – < 2bd22a0d40503a65d243b011de146603c8ce1cbc
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93205 badge
[![CVE-2026-93205](https://cveledger.app/badge/CVE-2026-93205.svg)](https://cveledger.app/cve/CVE-2026-93205)

Record last updated .