LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54034: iommufd: Make sure to zero vfio_iommu_type1_info before copying to user

In the Linux kernel, the following vulnerability has been resolved: iommufd: Make sure to zero vfio_iommu_type1_info before copying to user Missed a zero initialization here. Most of the struct is filled with a copy_from_user(), however minsz for that copy is smaller than the actual struct by 8 bytes, thus we don't fill the padding.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a small but security-relevant memory handling bug in iommufd. A structure was not fully zeroed before data was copied back to user space, leaving 8 bytes of padding uninitialized. The public record does not provide CVSS, CWE, impact scoring, or evidence of exploitation.

Executive priority

Handle through normal kernel patch governance unless internal exposure to VFIO/iommufd is broad or multi-tenant. There is no cited active exploitation or severity score, but kernel information leaks can matter in hardened or shared environments.

Technical view

The flaw affects iommufd handling of vfio_iommu_type1_info. The kernel copied user-provided data into most of the structure, but minsz was 8 bytes smaller than the full structure, leaving padding uninitialized before copying data to user space. The fix zero-initializes the structure first.

Likely exposure

Exposure appears limited to Linux kernels in the affected 6.2-era range listed by the CVE record. Systems without iommufd or VFIO-related usage may have lower practical exposure, but the provided sources do not define a precise runtime prerequisite.

Exploitation context

The source bundle provides no evidence of active exploitation, no KEV listing, no public exploit status, and no detailed attack path. Treat this as a local kernel information-disclosure-style concern unless vendor guidance states otherwise.

Researcher notes

The available record is sparse. The core condition is an unzeroed vfio_iommu_type1_info padding gap caused by minsz being smaller than the full structure. Avoid assuming broader memory corruption or privilege escalation without additional vendor or upstream analysis.

Mitigation direction

  • Check vendor kernel advisories for CVE-2023-54034 coverage.
  • Upgrade to a kernel build containing the referenced stable fixes.
  • Prioritize hosts using VFIO, virtualization, or device passthrough features.
  • Track distro backports instead of relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions across servers and endpoints.
  • Check whether vendor packages include the referenced stable commits.
  • Identify systems using iommufd, VFIO, or device passthrough workflows.
  • Confirm CVE status in vulnerability scanners after kernel updates.
Prepared
Confidence
medium
Sources
4

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-54034 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
3Source 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
LinuxLinuxd624d6652a65ad4f47a58b8651a1ec1163bb81d3, d624d6652a65ad4f47a58b8651a1ec1163bb81d3unaffected
LinuxLinux6.2, 0, 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.