Dependent-driver disruption via uninitialized descriptor fields
Published Dec 16, 2025 · Updated Dec 16, 2025
Use of uninitialized memory in the Linux kernel 6.4 and later allows attackers to disrupt dependent-driver probing via unspecified vectors. The S32CC pin-control probe allocates s32_pinctrl_desc without clearing every field, then passes an indeterminate num_custom_params value into device-tree configuration parsing. Reachability requires the S32CC driver and associated NXP hardware; no attacker-controlled trigger is disclosed, and the documented consequence is intermittent allocation and parse failure in dependent drivers.
Summary
What happened
Use of uninitialized memory in the Linux kernel 6.4 and later allows attackers to disrupt dependent-driver probing via unspecified vectors. The S32CC pin-control probe allocates s32_pinctrl_desc without clearing every field, then passes an indeterminate num_custom_params value into device-tree configuration parsing. Reachability requires the S32CC driver and associated NXP hardware; no attacker-controlled trigger is disclosed, and the documented consequence is intermittent allocation and parse failure in dependent drivers.
The record
- CVE
- CVE-2025-68222
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.4
- Affected versionversion=fd84aaa8173d3ff86f8df2009921336a1ea53a8a <3b90bd8aaeb21b513ecc4ed03299e80ece44a333
- Affected versionversion=fd84aaa8173d3ff86f8df2009921336a1ea53a8a <583ac7f65791ceda38ea1a493a4859f7161dcb03
- Affected versionversion=fd84aaa8173d3ff86f8df2009921336a1ea53a8a <7bbdd6c30e8fd92f7165b7730b038cfe42102004
- Affected versionversion=fd84aaa8173d3ff86f8df2009921336a1ea53a8a <97ea34defbb57bfaf71ce487b1b0865ffd186e81
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo