Linux Kernel up to 6.6.119/6.12.63/6.18.3 clk exynos_clkout_probe hws[] initialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.6.119/6.12.63/6.18.3. This impacts the function exynos_clkout_probe of the component clk. Performing a manipulation of the argument hws[] results in initialization. This vulnerability is reported as CVE-2025-71143. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.119/6.12.63/6.18.3. It has been classified as critical. This affects the function exynos_clkout_probe of the component clk. The manipulation of the argument hws[] with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. The summary by CVE is:

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 advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-71143 since 01/13/2026. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/25/2026).

The vulnerability scanner Nessus provides a plugin with the ID 299777 (Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-50112)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.6.120, 6.12.64, 6.18.4 or 6.19-rc1 eliminates this vulnerability. Applying the patch fbf57f5e453dadadb3d29b2d1dbe067e3dc4e236/eb1f3a6ab3efee2b52361879cdc2dc6b11f499c0/a317f63255ebc3dac378c79c5bff4f8d0561c290/cf33f0b7df13685234ccea7be7bfe316b60db4db is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (299777) and CERT Bund (WID-SEC-2026-0119). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.6
VulDB Meta Temp Score: 6.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 299777
Nessus Name: Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-50112)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.120/6.12.64/6.18.4/6.19-rc1
Patch: fbf57f5e453dadadb3d29b2d1dbe067e3dc4e236/eb1f3a6ab3efee2b52361879cdc2dc6b11f499c0/a317f63255ebc3dac378c79c5bff4f8d0561c290/cf33f0b7df13685234ccea7be7bfe316b60db4db

Timelineinfo

01/13/2026 CVE reserved
01/14/2026 +1 days Advisory disclosed
01/14/2026 +0 days VulDB entry created
03/25/2026 +70 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-71143 (🔒)
GCVE (CVE): GCVE-0-2025-71143
GCVE (VulDB): GCVE-100-341097
CERT Bund: WID-SEC-2026-0119 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 01/14/2026 17:52
Updated: 03/25/2026 23:19
Changes: 01/14/2026 17:52 (60), 01/16/2026 08:09 (7), 02/24/2026 14:02 (2), 03/25/2026 23:19 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!