Kernel panic via unchecked zero clock rate
Published Oct 14, 2026 · Updated Oct 14, 2026
Division by zero in the Linux kernel rtd119x watchdog allows attackers to cause a kernel panic during device initialization. The rtd119x_wdt_probe() function calculates max_timeout by dividing 0xffffffff by clk_get_rate() without rejecting a zero result. The failure requires the affected watchdog driver to probe with a zero clock rate; public evidence does not establish attacker control over that condition or required privileges.
Summary
What happened
Division by zero in the Linux kernel rtd119x watchdog allows attackers to cause a kernel panic during device initialization. The rtd119x_wdt_probe() function calculates max_timeout by dividing 0xffffffff by clk_get_rate() without rejecting a zero result. The failure requires the affected watchdog driver to probe with a zero clock rate; public evidence does not establish attacker control over that condition or required privileges.
The record
- CVE
- CVE-2026-98409
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started