CVE-2026-64236

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 12, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

i2c: davinci: fix division by zero on missing clock-frequency - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b694bc0e1831cbc5c3bbfd1b156ec719128f7d9
generic

i2c: davinci: fix division by zero on missing clock-frequency - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f43865cb64dd7cb50efae1281a95585617b12a1
generic

i2c: davinci: fix division by zero on missing clock-frequency - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-64236(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 23× in last 7d / 82× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 16:04 UTCEG score recompute
  2. 2026-08-25 16:04 UTCVendor advisory
  3. 2026-08-25 16:04 UTCGHSA enrichment
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 18:05 UTCEG score recompute
  6. 2026-08-24 18:05 UTCVendor advisory
  7. 2026-08-24 18:05 UTCGHSA enrichment
  8. 2026-08-23 19:32 UTCEG score recompute
  9. 2026-08-23 19:32 UTCVendor advisory
  10. 2026-08-23 19:32 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 21:32 UTCVendor advisory
  13. 2026-08-22 21:32 UTCGHSA enrichment
  14. 2026-08-21 23:32 UTCVendor advisory
  15. 2026-08-21 23:32 UTCGHSA enrichment
  16. 2026-08-21 01:31 UTCEG score recompute
  17. 2026-08-21 01:31 UTCVendor advisory
  18. 2026-08-21 01:31 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 03:32 UTCEG score recompute
  21. 2026-08-20 03:32 UTCVendor advisory
  22. 2026-08-20 03:32 UTCGHSA enrichment
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 05:23 UTCEG score recompute
  25. 2026-08-19 05:23 UTCVendor advisory
Show 66 more
  1. 2026-08-19 05:23 UTCGHSA enrichment
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-18 07:19 UTCEG score recompute
  4. 2026-08-18 07:19 UTCVendor advisory
  5. 2026-08-18 07:19 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 09:20 UTCEG score recompute
  8. 2026-08-17 09:20 UTCVendor advisory
  9. 2026-08-17 09:20 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 11:20 UTCEG score recompute
  12. 2026-08-16 11:20 UTCVendor advisory
  13. 2026-08-16 11:20 UTCGHSA enrichment
  14. 2026-08-15 13:21 UTCEG score recompute
  15. 2026-08-15 13:21 UTCVendor advisory
  16. 2026-08-15 13:21 UTCGHSA enrichment
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 15:21 UTCEG score recompute
  19. 2026-08-14 15:21 UTCVendor advisory
  20. 2026-08-14 15:21 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 17:21 UTCEG score recompute
  23. 2026-08-13 17:21 UTCVendor advisory
  24. 2026-08-13 17:21 UTCGHSA enrichment
  25. 2026-08-12 19:19 UTCEG score recompute▲ 5.50
  26. 2026-08-12 19:19 UTCVendor advisory
  27. 2026-08-12 19:19 UTCGHSA enrichment
  28. 2026-08-12 19:18 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-11 07:36 UTCVendor advisory
  31. 2026-08-11 07:36 UTCGHSA enrichment
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-09 13:47 UTCEPSS rescore
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 09:32 UTCVendor advisory
  36. 2026-08-08 09:32 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-05 11:28 UTCVendor advisory
  41. 2026-08-05 11:28 UTCGHSA enrichment
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 10:39 UTCEPSS rescore
  44. 2026-08-03 10:36 UTCEPSS rescore
  45. 2026-08-02 13:21 UTCVendor advisory
  46. 2026-08-02 13:21 UTCGHSA enrichment
  47. 2026-08-02 02:27 UTCEPSS rescore
  48. 2026-08-01 04:16 UTCEPSS rescore
  49. 2026-07-30 16:28 UTCEPSS rescore
  50. 2026-07-30 15:16 UTCEG score recompute
  51. 2026-07-30 15:16 UTCGHSA enrichment
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-30 01:30 UTCEPSS rescore
  54. 2026-07-29 01:03 UTCEG score recompute
  55. 2026-07-29 01:03 UTCGHSA enrichment
  56. 2026-07-28 15:37 UTCEPSS rescore
  57. 2026-07-27 14:14 UTCEPSS rescore
  58. 2026-07-26 14:54 UTCEPSS rescore
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-26 02:58 UTCEG score recompute
  61. 2026-07-26 02:58 UTCGHSA enrichment
  62. 2026-07-25 14:18 UTCEPSS rescore
  63. 2026-07-25 14:18 UTCEPSS rescore
  64. 2026-07-24 16:31 UTCNVD update
  65. 2026-07-24 15:43 UTCEG score recompute
  66. 2026-07-24 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64236?
CVE-2026-64236 is a medium vulnerability published on July 24, 2026. 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 DAVINCII2CDEFAULTBUSFREQ. However, this macro was defined in kHz (100),…
When was CVE-2026-64236 disclosed?
CVE-2026-64236 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64236 actively exploited?
CVE-2026-64236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64236?
CVE-2026-64236 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64236, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64236

Explore →

Is Your Infrastructure Affected by CVE-2026-64236?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs