[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122438-CVE-2023-54034-3089@gregkh>
Date: Wed, 24 Dec 2025 11:57:18 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54034: iommufd: Make sure to zero vfio_iommu_type1_info before copying to user
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2023-54034 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit d624d6652a65ad4f47a58b8651a1ec1163bb81d3 and fixed in 6.2.3 with commit 7adcec686e4d699c169d34c722132b2bce5232cb
Issue introduced in 6.2 with commit d624d6652a65ad4f47a58b8651a1ec1163bb81d3 and fixed in 6.3 with commit b3551ead616318ea155558cdbe7e91495b8d9b33
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-54034
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/iommu/iommufd/vfio_compat.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/7adcec686e4d699c169d34c722132b2bce5232cb
https://git.kernel.org/stable/c/b3551ead616318ea155558cdbe7e91495b8d9b33
Powered by blists - more mailing lists