LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53482: iommu: Fix error unwind in iommu_group_alloc()

In the Linux kernel, the following vulnerability has been resolved: iommu: Fix error unwind in iommu_group_alloc() If either iommu_group_grate_file() fails then the iommu_group is leaked. Destroy it on these error paths. Found by kselftest/iommu/iommufd_fail_nth

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2023-53482 is a Linux kernel IOMMU resource-leak bug. When a specific group-allocation error path fails, the kernel can leak an iommu_group object. Public sources do not provide a CVSS score, real-world exploitation evidence, or a broad business-impact assessment.

Executive priority

Handle through normal Linux kernel patch management. Escalate only for heavily virtualized or hardware-passthrough environments, or if your vendor assigns higher severity. Current public evidence does not support emergency response.

Technical view

The Linux kernel fixed error unwinding in iommu_group_alloc(). If iommu_group_create_file() fails on certain paths, the allocated iommu_group is not destroyed. The fix destroys the group on those error paths. The issue was found by kselftest/iommu/iommufd_fail_nth.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds containing the vulnerable IOMMU code. The source bundle lists Linux kernel version entries including 4.11, 5.15.99, 6.1.16, 6.2.3, and 6.3, but downstream distro status must be verified separately.

Exploitation context

No CISA KEV listing is present, and the provided sources do not claim active exploitation. The bug requires an error path in IOMMU group allocation. Public evidence supports a resource-leak condition, not code execution or privilege escalation.

Researcher notes

The public record is sparse: no CVSS, CWE, or exploitation details are provided. The clearest technical signal is the stable-kernel fix for an allocation error-unwind leak in IOMMU group handling. Avoid assuming exploitability beyond resource leakage without additional kernel or vendor analysis.

Mitigation direction

  • Check your Linux vendor or distribution advisory for CVE-2023-53482 status.
  • Update to a kernel build that includes the referenced stable fixes.
  • Prioritize systems using IOMMU, virtualization, passthrough, or device isolation features.
  • Track this as lower urgency unless vendor guidance rates it higher.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Confirm whether vendor kernels include the referenced stable commits.
  • Review kernel changelogs or package advisories for CVE-2023-53482.
  • Monitor for updated CVSS, distro advisories, or exploit evidence.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2023-53482 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbc7d12b91bd35477fd650c4d72b61239de9d9066, bc7d12b91bd35477fd650c4d72b61239de9d9066, bc7d12b91bd35477fd650c4d72b61239de9d9066, bc7d12b91bd35477fd650c4d72b61239de9d9066unaffected
LinuxLinux4.11, 0, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.