CVE-2026-64236: Linux kernel · i2c: davinci: fix division by zero on missing clock-frequency
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 27 Oct 2026, 20:27 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
A fix is available that redefines the fallback clock frequency to the correct unit (Hz) in the Linux kernel source code. Applying the official Linux kernel update that includes this fix will resolve the issue.
Description
A division-by-zero vulnerability was identified and fixed in the Linux kernel's i2c davinci driver. The issue occurred when the 'clock-frequency' property was missing from the device tree, causing the driver to use a fallback frequency defined in kHz instead of Hz. This mismatch led to integer truncation and a zero bus frequency, resulting in a kernel panic during clock divider calculations. The fix involved redefining the fallback frequency in Hz to align with the expected units, preventing the division-by-zero error.