Menu

Star on GitHub · 3.2k

CVE-2025-40127

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 in…

Published Nov 12, 2025EPSS 0.22%

Overview

CVE-2025-40127 is a known-severity vulnerability. It was published on November 12, 2025.

Technical description

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(+)

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-40127?

CVE-2025-40127 is a known-severity vulnerability. It was published on November 12, 2025.

How severe is CVE-2025-40127?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-40127?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-40127?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-40127 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.