CVE-2026-98408

Kernel panic via unchecked watchdog clock rate

Published Oct 14, 2026 · Updated Oct 14, 2026

Division by zero in the RZ/V2H watchdog driver in Linux Kernel 6.12 allows attackers to crash the kernel during initialization. The rzv2h_wdt_probe() function in drivers/watchdog/rzv2h_wdt.c divides the maximum hardware heartbeat calculation by clk_get_rate(count_clk) without rejecting zero. The panic requires initialization of the affected watchdog with a zero count-clock rate; public evidence does not establish attacker control over that condition or a remote trigger.

CVSS severityUnavailable
Unscored
EPSS probability0.21%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Division by zero in the RZ/V2H watchdog driver in Linux Kernel 6.12 allows attackers to crash the kernel during initialization. The rzv2h_wdt_probe() function in drivers/watchdog/rzv2h_wdt.c divides the maximum hardware heartbeat calculation by clk_get_rate(count_clk) without rejecting zero. The panic requires initialization of the affected watchdog with a zero count-clock rate; public evidence does not establish attacker control over that condition or a remote trigger.

The record

CVE
CVE-2026-98408
Published
Oct 14, 2026
Updated
Oct 14, 2026
Vendor
Linux Foundation
Product
Linux Kernel
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Oct 14, 2026CVE publishedPublication date reported by the CVE source.
  2. 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?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.12
  2. Affected versionversion=f6febd0a30b6e299a08076116256e3b36c24eada <0dd78d9d9b546de08e2ae391541f48cea0a9b842
  3. Affected versionversion=f6febd0a30b6e299a08076116256e3b36c24eada <6274281c41efa8dd1aa5234c59ad904ff89d7af4
  4. Affected versionversion=f6febd0a30b6e299a08076116256e3b36c24eada <eb14ee406e1d0fbbfb857f0eaa710daa8c2dc30e

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

Linux Foundation · Linux Kernelversion=6.12; version=f6febd0a30b6e299a08076116256e3b36c24eada <0dd78d9d9b546de08e2ae391541f48cea0a9b842; version=f6febd0a30b6e299a08076116256e3b36c24eada <6274281c41efa8dd1aa5234c59ad904ff89d7af4; version=f6febd0a30b6e299a08076116256e3b36c24eada <eb14ee406e1d0fbbfb857f0eaa710daa8c2dc30e

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

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