Linux Kernel up to 6.18.34/7.0.11 davinci probe clock-frequency divide by zero

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.2	$0-$5k	3.11

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.18.34/7.0.11. The affected element is the function probe of the component davinci. Performing a manipulation of the argument clock-frequency results in divide by zero. This vulnerability is identified as CVE-2026-64236. The attack is only possible with local access. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.18.34/7.0.11. This affects the function probe of the component davinci. The manipulation of the argument clock-frequency with an unknown input leads to a divide by zero vulnerability. CWE is classifying the issue as CWE-369. The product divides a value by zero. This is going to have an impact on availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: i2c: davinci: fix division by zero on missing clock-frequency When the 'clock-frequency' property is missing from the device tree, the driver falls back to DAVINCI_I2C_DEFAULT_BUS_FREQ. However, this macro was defined in kHz (100), whereas the device tree property is expected in Hz. The probe function divided the fallback value by 1000, causing integer truncation that resulted in dev->bus_freq = 0. This triggered a deterministic division-by-zero kernel panic when calculating clock dividers later in the probe sequence. Fix this by redefining DAVINCI_I2C_DEFAULT_BUS_FREQ in Hz (100000) to match the expected device tree property unit, allowing the existing division logic to work correctly for both cases.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-64236 since 07/19/2026. The exploitability is told to be easy. Attacking locally is a requirement. The exploitation needs additional levels of successful authentication. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 6.18.35 or 7.0.12 eliminates this vulnerability. Applying the patch 3f43865cb64dd7cb50efae1281a95585617b12a1/9b694bc0e1831cbc5c3bbfd1b156ec719128f7d9/030675aa54cf757769b3db65642433d626b3ed7c is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.18.0
• 6.18.1
• 6.18.2
• 6.18.3
• 6.18.4
• 6.18.5
• 6.18.6
• 6.18.7
• 6.18.8
• 6.18.9
• 6.18.10
• 6.18.11
• 6.18.12
• 6.18.13
• 6.18.14
• 6.18.15
• 6.18.16
• 6.18.17
• 6.18.18
• 6.18.19
• 6.18.20
• 6.18.21
• 6.18.22
• 6.18.23
• 6.18.24
• 6.18.25
• 6.18.26
• 6.18.27
• 6.18.28
• 6.18.29
• 6.18.30
• 6.18.31
• 6.18.32
• 6.18.33
• 6.18.34
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.0.8
• 7.0.9
• 7.0.10
• 7.0.11

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Divide by zero
CWE: CWE-369 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.18.35/7.0.12
Patch: 3f43865cb64dd7cb50efae1281a95585617b12a1/9b694bc0e1831cbc5c3bbfd1b156ec719128f7d9/030675aa54cf757769b3db65642433d626b3ed7c

Timelineinfo

07/19/2026 CVE reserved
07/24/2026 +5 days Advisory disclosed
07/24/2026 +0 days VulDB entry created
07/24/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64236 (🔒)
GCVE (CVE): GCVE-0-2026-64236
GCVE (VulDB): GCVE-100-382971

Entryinfo

Created: 07/24/2026 18:44
Changes: 07/24/2026 18:44 (60)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

Want to stay up to date on a daily basis?

Enable the mail alert feature now!