CVE-2023-54137
Last modified
CVE-2023-54137 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= ad721705d09c62f0d108a6b4f59867ebfd592c90, < ad83d83dd891244de0d07678b257dc976db7c132; >= ad721705d09c62f0d108a6b4f59867ebfd592c90, < 13fd667db999bffb557c5de7adb3c14f1713dd51; >= ad721705d09c62f0d108a6b4f59867ebfd592c90, < f6f300ecc196d243c02adeb9ee0c62c677c24bfb; >= ad721705d09c62f0d108a6b4f59867ebfd592c90, < cbac29a1caa49a34e131394e1f4d924a76d8b0c9; >= ad721705d09c62f0d108a6b4f59867ebfd592c90, < 1b5feb8497cdb5b9962db2700814bffbc030fb4a; >= ad721705d09c62f0d108a6b4f59867ebfd592c90, < cd24e2a60af633f157d7e59c0a6dba64f131c0b1 |
| Linux | Linux | 5.8 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-54137?
How severe is CVE-2023-54137?
How do I fix CVE-2023-54137?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-54131In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54132In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54133In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54134In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54135In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54136In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54138In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54139In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-5414The Icegram Express plugin for WordPress is vulnerable to Di…7.2
- CVE-2023-54140In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54141In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54142In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2023-54137?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
