What is CVE-2026-64236?

CVE-2026-64236 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Divide By Zero flaw (CWE-369), affecting Linux kernel versions from 6.14 onward and patched in 6.18.35, 7.0.12 and 7.1. CVE-2026-64236 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-64236?

CVE-2026-64236 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-64236?

Yes, CVE-2026-64236 has been patched. Fixed versions include 6.18.35, 7.0.12 and 7.1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-64236 actively exploited?

CVE-2026-64236 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Divide By Zero (CWE-369)?

The product divides a value by zero, causing a crash or unexpected behaviour. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/369.html

CVE-2026-64236

Medium

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.

Package Linux Kernel

Published 2026-07-24

Last modified 2026-08-12

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-369

CVE-2026-64236 is a Divide By Zero vulnerability

What is Divide By Zero?

The product divides a value by zero, causing a crash or unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.14 and later are affected. Fixed in 6.18.35, 7.0.12, 7.1 and their respective stable series.

Affected from

≥ 6.14

Fixed in

✓ 6.18.35 6.18.x ✓ 7.0.12 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/030675aa54cf757769b3db65642433d626b3ed7c

Patch
Kernel Git
https://git.kernel.org/stable/c/3f43865cb64dd7cb50efae1281a95585617b12a1

Patch
Kernel Git
https://git.kernel.org/stable/c/9b694bc0e1831cbc5c3bbfd1b156ec719128f7d9

Patch

Details

CVE ID CVE-2026-64236

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-07-24

Modified 2026-08-12

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64236?

CVE-2026-64236 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a Divide By Zero flaw (CWE-369) . It affects Linux kernel versions from 6.14 onward and has been patched in 6.18.35, 7.0.12 and 7.1. CVE-2026-64236 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64236?

CVE-2026-64236 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-64236?

Yes. CVE-2026-64236 has been patched. Fixed versions include 6.18.35, 7.0.12 and 7.1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-64236 actively exploited?

No. CVE-2026-64236 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.