[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100709-CVE-2023-53684-db58@gregkh>
Date: Tue, 7 Oct 2025 17:21:43 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53684: xfrm: Zero padding when dumping algos and encap
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
xfrm: Zero padding when dumping algos and encap
When copying data to user-space we should ensure that only valid
data is copied over. Padding in structures may be filled with
random (possibly sensitve) data and should never be given directly
to user-space.
This patch fixes the copying of xfrm algorithms and the encap
template in xfrm_user so that padding is zeroed.
The Linux kernel CVE team has assigned CVE-2023-53684 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.106 with commit 0725daaa9a879388ed312110f62dbd5ea2d75f8f
Fixed in 6.1.23 with commit 5218af4ad5d8948faac19f71583bcd786c3852df
Fixed in 6.2.10 with commit 1a351e26cc010d6991fbbd5701ac16581372e26f
Fixed in 6.3 with commit 8222d5910dae08213b6d9d4bc9a7f8502855e624
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-53684
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:
net/xfrm/xfrm_user.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/0725daaa9a879388ed312110f62dbd5ea2d75f8f
https://git.kernel.org/stable/c/5218af4ad5d8948faac19f71583bcd786c3852df
https://git.kernel.org/stable/c/1a351e26cc010d6991fbbd5701ac16581372e26f
https://git.kernel.org/stable/c/8222d5910dae08213b6d9d4bc9a7f8502855e624
Powered by blists - more mailing lists