vfio/type1: fix cap_migration information leak
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ad721705d09c62f0d108a6b4f59867ebfd592c90 · < cd24e2a60af633f157d7e59c0a6dba64f131c0b1| No fix yet |
| Linux Linux |
|
|
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 */ };
From the CVE record · Linux
An uninitialized four-byte hole in the Linux kernel's VFIO migration capability structure can be copied to userspace. A local caller able to invoke ioctl(VFIO_IOMMU_GET_INFO) may receive stack data; authentication requirements are not specified, and no user interaction is described.
Engineers running the Linux kernel should check their installations; affected versions are not specified.