Driver initialization failure via uninitialized clock pointer
Published Nov 12, 2025 · Updated May 11, 2026
Division by zero in the ks-sa hardware RNG driver in affected Linux kernel releases interrupts driver initialization via unspecified vectors. The ks_sa_rng_init function passes an uninitialized clock pointer to clk_get_rate and divides by the resulting zero rate while calculating delay values. The condition requires a TI Keystone SA hardware RNG device, and published material identifies no attacker-controlled trigger or consequence beyond failed driver initialization.
Summary
What happened
Division by zero in the ks-sa hardware RNG driver in affected Linux kernel releases interrupts driver initialization via unspecified vectors. The ks_sa_rng_init function passes an uninitialized clock pointer to clk_get_rate and divides by the resulting zero rate while calculating delay values. The condition requires a TI Keystone SA hardware RNG device, and published material identifies no attacker-controlled trigger or consequence beyond failed driver initialization.
The record
- CVE
- CVE-2025-40127
- Published
- Nov 12, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=5.5
- Affected versionversion=6d01d8511dceb9cd40f72eb102b7d24f0b2e997b <2b6bcce32cb5aff84588a844a4d3f6dd5353b8e2
- Affected versionversion=6d01d8511dceb9cd40f72eb102b7d24f0b2e997b <55a70e1de75e5ff5f961c79a2cdc6a4468cc2bf2
- Affected versionversion=6d01d8511dceb9cd40f72eb102b7d24f0b2e997b <612b1dfeb414dfa780a6316014ceddf9a74ff5c0
- Affected versionversion=6d01d8511dceb9cd40f72eb102b7d24f0b2e997b <692a04a1e0cde1d80a33df0078c755cf02cd7268
- Affected versionversion=6d01d8511dceb9cd40f72eb102b7d24f0b2e997b <d76b099011fa056950f63d05ebb6160991242f6a
- Affected versionversion=6d01d8511dceb9cd40f72eb102b7d24f0b2e997b <eec7e0e19c1fa75dc65e25aa6a21ef24a03849af
- Affected versionversion=6d01d8511dceb9cd40f72eb102b7d24f0b2e997b <f4238064379a91e71a9c258996acac43c50c2094
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