linux-cve-announce - CVE-2023-53000: netlink: prevent potential spectre v1 gadgets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025032711-CVE-2023-53000-fded@gregkh>
Date: Thu, 27 Mar 2025 17:43:47 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-53000: netlink: prevent potential spectre v1 gadgets

Description
===========

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

netlink: prevent potential spectre v1 gadgets

Most netlink attributes are parsed and validated from
__nla_validate_parse() or validate_nla()

    u16 type = nla_type(nla);

    if (type == 0 || type > maxtype) {
        /* error or continue */
    }

@type is then used as an array index and can be used
as a Spectre v1 gadget.

array_index_nospec() can be used to prevent leaking
content of kernel memory to malicious users.

This should take care of vast majority of netlink uses,
but an audit is needed to take care of others where
validation is not yet centralized in core netlink functions.

The Linux kernel CVE team has assigned CVE-2023-53000 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.15 with commit bfa83a9e03cf8d501c6272999843470afecb32ed and fixed in 5.4.231 with commit 3e5082b1c66c7783fbcd79b5b178573230e528ff
	Issue introduced in 2.6.15 with commit bfa83a9e03cf8d501c6272999843470afecb32ed and fixed in 5.10.166 with commit 539ca5dcbc91134bbe2c45677811c31d8b030d2d
	Issue introduced in 2.6.15 with commit bfa83a9e03cf8d501c6272999843470afecb32ed and fixed in 5.15.91 with commit 41b74e95f297ac360ca7ed6bf200100717cb6c45
	Issue introduced in 2.6.15 with commit bfa83a9e03cf8d501c6272999843470afecb32ed and fixed in 6.1.9 with commit 992e4ff7116a77968039277b5d6aaa535c2f2184
	Issue introduced in 2.6.15 with commit bfa83a9e03cf8d501c6272999843470afecb32ed and fixed in 6.2 with commit f0950402e8c76e7dcb08563f1b4e8000fbc62455

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-53000
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:
	lib/nlattr.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/3e5082b1c66c7783fbcd79b5b178573230e528ff
	https://git.kernel.org/stable/c/539ca5dcbc91134bbe2c45677811c31d8b030d2d
	https://git.kernel.org/stable/c/41b74e95f297ac360ca7ed6bf200100717cb6c45
	https://git.kernel.org/stable/c/992e4ff7116a77968039277b5d6aaa535c2f2184
	https://git.kernel.org/stable/c/f0950402e8c76e7dcb08563f1b4e8000fbc62455