Security readout for executives and security teams
Plain-English summary
A Linux kernel cleanup error can access memory after it has been freed when an IOMMU Shared Virtual Addressing binding is removed. This can crash an affected system. The supplied CVSS score is 7.8, but the source bundle provides no evidence of active exploitation.
Executive priority
Treat this as a high-priority patch-validation issue for affected multi-user or compute systems using IOMMU SVA. Expedite inventory and vendor confirmation, but current sources do not justify declaring an exploitation emergency. Version ambiguity makes vendor-specific verification essential.
Technical view
iommu_sva_unbind_device() may access domain->mm->iommu_mm after iommu_domain_free() releases the associated mm structure. This use-after-free can cause a kernel crash. The stable fix moves the access before domain destruction. The CVSS vector describes a local, low-complexity, low-privilege path without user interaction.
Likely exposure
Systems are potentially exposed when running a build identified as affected and exercising the IOMMU/SVA device-unbind path. The bundle lists 6.18.20, 6.19, 6.19.10, and 7.0, plus an ambiguous "0" entry. Because its version data is inconsistent, confirm downstream vendor backports rather than relying only on release numbers.
Exploitation context
The bundle marks this CVE as absent from KEV and supplies no report of exploitation or public exploit availability. The CVSS vector indicates local access and low privileges are required. The documented outcome is a crash; the description does not substantiate practical confidentiality or integrity compromise despite the CVSS impact metrics.
Researcher notes
The defect is a lifetime-ordering error: iommu_domain_free() can ultimately invoke mm_pasid_drop(), freeing the mm-related state before a later iommu_mm access. Moving that access earlier prevents the freed-structure dereference. The bundle establishes crash potential but does not document trigger reliability, affected hardware requirements, exploitability beyond denial of service, or observed attacks.
Mitigation direction
- Apply the applicable vendor kernel update containing the referenced stable fix.
- Check distribution advisories and package changelogs for downstream backport status.
- Prioritize affected systems that use IOMMU Shared Virtual Addressing.
Validation and detection
- Inventory deployed kernel builds and compare them with vendor advisories.
- Check package metadata for the referenced commits or an equivalent backport.
- Determine whether IOMMU Shared Virtual Addressing is enabled and used.
- After updating, confirm the fixed kernel is active across all targeted systems.
- Review kernel logs for crashes associated with IOMMU/SVA device unbinding.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2026-23429 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/58abeb7b9562f25bdfa2f5ae5ce803eb02e74433CVE reference, Linux
- https://git.kernel.org/stable/c/f5daaa2c959d9f894fb5b1ab76da8612dd220a0dCVE reference, Linux
- https://git.kernel.org/stable/c/06e14c36e20b48171df13d51b89fe67c594ed07aCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.