linux-cve-announce - CVE-2025-71143: clk: samsung: exynos-clkout: Assign .num before accessing .hws

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2026011456-CVE-2025-71143-5787@gregkh>
Date: Wed, 14 Jan 2026 16:08:07 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-71143: clk: samsung: exynos-clkout: Assign .num before accessing .hws

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

clk: samsung: exynos-clkout: Assign .num before accessing .hws

Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with
__counted_by") annotated the hws member of 'struct clk_hw_onecell_data'
with __counted_by, which informs the bounds sanitizer (UBSAN_BOUNDS)
about the number of elements in .hws[], so that it can warn when .hws[]
is accessed out of bounds. As noted in that change, the __counted_by
member must be initialized with the number of elements before the first
array access happens, otherwise there will be a warning from each access
prior to the initialization because the number of elements is zero. This
occurs in exynos_clkout_probe() due to .num being assigned after .hws[]
has been accessed:

  UBSAN: array-index-out-of-bounds in drivers/clk/samsung/clk-exynos-clkout.c:178:18
  index 0 is out of range for type 'clk_hw *[*]'

Move the .num initialization to before the first access of .hws[],
clearing up the warning.

The Linux kernel CVE team has assigned CVE-2025-71143 to this issue.


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

	Issue introduced in 6.6 with commit f316cdff8d677db9ad9c90acb44c4cd535b0ee27 and fixed in 6.6.120 with commit fbf57f5e453dadadb3d29b2d1dbe067e3dc4e236
	Issue introduced in 6.6 with commit f316cdff8d677db9ad9c90acb44c4cd535b0ee27 and fixed in 6.12.64 with commit eb1f3a6ab3efee2b52361879cdc2dc6b11f499c0
	Issue introduced in 6.6 with commit f316cdff8d677db9ad9c90acb44c4cd535b0ee27 and fixed in 6.18.4 with commit a317f63255ebc3dac378c79c5bff4f8d0561c290
	Issue introduced in 6.6 with commit f316cdff8d677db9ad9c90acb44c4cd535b0ee27 and fixed in 6.19-rc1 with commit cf33f0b7df13685234ccea7be7bfe316b60db4db

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-2025-71143
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/clk/samsung/clk-exynos-clkout.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/fbf57f5e453dadadb3d29b2d1dbe067e3dc4e236
	https://git.kernel.org/stable/c/eb1f3a6ab3efee2b52361879cdc2dc6b11f499c0
	https://git.kernel.org/stable/c/a317f63255ebc3dac378c79c5bff4f8d0561c290
	https://git.kernel.org/stable/c/cf33f0b7df13685234ccea7be7bfe316b60db4db