nday
CVE-2023-54137

vfio/type1: fix cap_migration information leak

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2025-12-24T13:06Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

vfio/type1: fix cap_migration information leak

Fix an information leak where an uninitialized hole in struct vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace.

The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as shown in this pahole(1) output:

struct vfio_iommu_type1_info_cap_migration {
        struct vfio_info_cap_header header;              /*     0     8 */
        __u32                      flags;                /*     8     4 */

        /* XXX 4 bytes hole, try to pack */

        __u64                      pgsize_bitmap;        /*    16     8 */
        __u64                      max_dirty_bitmap_size; /*    24     8 */

        /* size: 32, cachelines: 1, members: 4 */
        /* sum members: 28, holes: 1, sum holes: 4 */
        /* last cacheline: 32 bytes */
};

The cap_mig variable is filled in without initializing the hole:

static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,
                       struct vfio_info_cap *caps)
{
    struct vfio_iommu_type1_info_cap_migration cap_mig;

    cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;
    cap_mig.header.version = 1;

    cap_mig.flags = 0;
    /* support minimum pgsize */
    cap_mig.pgsize_bitmap = (size_t)1 << __ffs(iommu->pgsize_bitmap);
    cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;

    return vfio_info_add_capability(caps, &cap_mig.header, sizeof(cap_mig));
}

The structure is then copied to a temporary location on the heap. At this point it's already too late and ioctl(VFIO_IOMMU_GET_INFO) copies it to userspace later:

int vfio_info_add_capability(struct vfio_info_cap *caps,
                 struct vfio_info_cap_header *cap, size_t size)
{
    struct vfio_info_cap_header *header;

    header = vfio_info_cap_add(caps, size, cap->id, cap->version);
    if (IS_ERR(header))
        return PTR_ERR(header);

    memcpy(header + 1, cap + 1, size - sizeof(*header));

    return 0;
}

This issue was found by code inspection.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 310232,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2023-54137",
  "occurred_at": "2025-12-24T13:06:52.689Z",
  "observed_at": "2026-11-13T05:38:14.046808Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2025-12-24T13:06:52.689Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.