CVE-2025-40127: hwrng: ks-sa - fix division by zero in ks_sa_rng_init
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 2b6bcce32cb5aff84588a844a4d3f6dd5353b8e2, 55a70e1de75e5ff5f961c79a2cdc6a4468cc2bf2, 612b1dfeb414dfa780a6316014ceddf9a74ff5c0.
Low priority for now. Upgrade to Linux Linux 2b6bcce32cb5aff84588a844a4d3f6dd5353b8e2, 55a70e1de75e5ff5f961c79a2cdc6a4468cc2bf2, 612b1dfeb414dfa780a6316014ceddf9a74ff5c0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: hwrng: ks-sa - fix division by zero in ks_sa_rng_init Fix division by zero in ks_sa_rng_init caused by missing clock pointer initialization. The clk_get_rate() call is performed on an uninitialized clk pointer, resulting in division by zero when calculating delay values. Add clock initialization code before using the clock. drivers/char/hw_random/ks-sa-rng.c | 7 +++++++ 1 file changed, 7 insertions(+)
- Published
- Nov 12, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 6d01d8511dceb9cd40f72eb102b7d24f0b2e997b and later · before 692a04a1e0cde1d80a33df0078c755cf02cd7268affected · git
- 6d01d8511dceb9cd40f72eb102b7d24f0b2e997b and later · before d76b099011fa056950f63d05ebb6160991242f6aaffected · git
- 6d01d8511dceb9cd40f72eb102b7d24f0b2e997b and later · before eec7e0e19c1fa75dc65e25aa6a21ef24a03849afaffected · git
- 6d01d8511dceb9cd40f72eb102b7d24f0b2e997b and later · before f4238064379a91e71a9c258996acac43c50c2094affected · git
- 6d01d8511dceb9cd40f72eb102b7d24f0b2e997b and later · before 2b6bcce32cb5aff84588a844a4d3f6dd5353b8e2affected · git
- 6d01d8511dceb9cd40f72eb102b7d24f0b2e997b and later · before 55a70e1de75e5ff5f961c79a2cdc6a4468cc2bf2affected · git
- 6d01d8511dceb9cd40f72eb102b7d24f0b2e997b and later · before 612b1dfeb414dfa780a6316014ceddf9a74ff5c0affected · git
- before 5.5not affected · semver
- 5.10.246 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40125Nov 12, 2025 · blk-mq: check kobject state_in_sysfs before deleting in blk_mq_unregister_hctx0Monitor
- ← EarlierCVE-2025-40126Nov 12, 2025 · sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC0Monitor
- Later →CVE-2025-40129Nov 12, 2025 · sunrpc: fix null pointer dereference on zero-length checksum30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2b6bcce32cb5aff84588a844a4d3f6dd5353b8e2 | Vendor (CNA) |
| Linux Linux | 55a70e1de75e5ff5f961c79a2cdc6a4468cc2bf2 | Vendor (CNA) |
| Linux Linux | 612b1dfeb414dfa780a6316014ceddf9a74ff5c0 | Vendor (CNA) |
| Linux Linux | 692a04a1e0cde1d80a33df0078c755cf02cd7268 | Vendor (CNA) |
| Linux Linux | d76b099011fa056950f63d05ebb6160991242f6a | Vendor (CNA) |
| Linux Linux | eec7e0e19c1fa75dc65e25aa6a21ef24a03849af | Vendor (CNA) |
| Linux Linux | f4238064379a91e71a9c258996acac43c50c2094 | Vendor (CNA) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/55a70e1de75e5ff5f961c79a2cdc6a4468cc2bf2
- git.kernel.org/stable/c/612b1dfeb414dfa780a6316014ceddf9a74ff5c0
- git.kernel.org/stable/c/692a04a1e0cde1d80a33df0078c755cf02cd7268
- git.kernel.org/stable/c/d76b099011fa056950f63d05ebb6160991242f6a
- git.kernel.org/stable/c/eec7e0e19c1fa75dc65e25aa6a21ef24a03849af
- git.kernel.org/stable/c/f4238064379a91e71a9c258996acac43c50c2094
Vendor advisories and official records. Exploit/PoC links are deliberately left out.