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(4)

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 (141 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(4)

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 19× in last 7d / 86× 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.

Showing the most recent 100 of 158 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 07:59 UTCEG score recompute
  3. 2026-09-18 07:59 UTCVendor advisory
  4. 2026-09-18 07:59 UTCGHSA enrichment
  5. 2026-09-17 09:59 UTCEG score recompute
  6. 2026-09-17 09:59 UTCVendor advisory
  7. 2026-09-17 09:59 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 11:59 UTCVendor advisory
  10. 2026-09-16 11:59 UTCGHSA enrichment
  11. 2026-09-15 09:37 UTCEG score recompute
  12. 2026-09-15 09:37 UTCVendor advisory
  13. 2026-09-15 09:37 UTCGHSA enrichment
  14. 2026-09-14 10:43 UTCEG score recompute
  15. 2026-09-14 10:43 UTCVendor advisory
  16. 2026-09-14 10:43 UTCGHSA enrichment
  17. 2026-09-13 12:39 UTCEG score recompute
  18. 2026-09-13 12:39 UTCVendor advisory
  19. 2026-09-13 12:39 UTCGHSA enrichment
  20. 2026-09-12 14:37 UTCVendor advisory
  21. 2026-09-12 14:37 UTCGHSA enrichment
  22. 2026-09-11 16:37 UTCEG score recompute
  23. 2026-09-11 16:37 UTCVendor advisory
  24. 2026-09-11 16:37 UTCGHSA enrichment
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 14:43 UTCEG score recompute
  2. 2026-09-10 14:43 UTCVendor advisory
  3. 2026-09-10 14:43 UTCGHSA enrichment
  4. 2026-09-09 08:47 UTCEG score recompute
  5. 2026-09-09 08:47 UTCVendor advisory
  6. 2026-09-09 08:47 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 21:25 UTCEG score recompute
  9. 2026-09-07 21:25 UTCVendor advisory
  10. 2026-09-07 21:25 UTCGHSA enrichment
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 17:25 UTCEG score recompute
  13. 2026-09-06 17:25 UTCVendor advisory
  14. 2026-09-06 17:25 UTCGHSA enrichment
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 19:24 UTCEG score recompute
  17. 2026-09-05 19:24 UTCVendor advisory
  18. 2026-09-05 19:23 UTCGHSA enrichment
  19. 2026-09-05 15:31 UTCEPSS rescore
  20. 2026-09-04 12:51 UTCEG score recompute
  21. 2026-09-04 12:51 UTCGHSA enrichment
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 23:16 UTCEG score recompute
  25. 2026-09-01 23:16 UTCVendor advisory
  26. 2026-09-01 23:16 UTCGHSA enrichment
  27. 2026-09-01 13:54 UTCEPSS rescore
  28. 2026-09-01 04:40 UTCEPSS rescore
  29. 2026-08-30 22:19 UTCEG score recompute
  30. 2026-08-30 22:19 UTCVendor advisory
  31. 2026-08-30 22:19 UTCGHSA enrichment
  32. 2026-08-30 19:17 UTCEPSS rescore
  33. 2026-08-30 00:18 UTCEG score recompute
  34. 2026-08-30 00:18 UTCVendor advisory
  35. 2026-08-30 00:18 UTCGHSA enrichment
  36. 2026-08-28 21:42 UTCEPSS rescore
  37. 2026-08-27 12:15 UTCEG score recompute
  38. 2026-08-27 12:15 UTCVendor advisory
  39. 2026-08-27 12:15 UTCGHSA enrichment
  40. 2026-08-26 14:47 UTCEPSS rescore
  41. 2026-08-26 14:15 UTCVendor advisory
  42. 2026-08-26 14:15 UTCGHSA enrichment
  43. 2026-08-25 16:04 UTCEG score recompute
  44. 2026-08-25 16:04 UTCVendor advisory
  45. 2026-08-25 16:04 UTCGHSA enrichment
  46. 2026-08-25 13:49 UTCEPSS rescore
  47. 2026-08-24 18:05 UTCEG score recompute
  48. 2026-08-24 18:05 UTCVendor advisory
  49. 2026-08-24 18:05 UTCGHSA enrichment
  50. 2026-08-23 19:32 UTCEG score recompute
  51. 2026-08-23 19:32 UTCVendor advisory
  52. 2026-08-23 19:32 UTCGHSA enrichment
  53. 2026-08-23 00:19 UTCEPSS rescore
  54. 2026-08-22 21:32 UTCVendor advisory
  55. 2026-08-22 21:32 UTCGHSA enrichment
  56. 2026-08-21 23:32 UTCVendor advisory
  57. 2026-08-21 23:32 UTCGHSA enrichment
  58. 2026-08-21 01:31 UTCEG score recompute
  59. 2026-08-21 01:31 UTCVendor advisory
  60. 2026-08-21 01:31 UTCGHSA enrichment
  61. 2026-08-20 22:55 UTCEPSS rescore
  62. 2026-08-20 03:32 UTCEG score recompute
  63. 2026-08-20 03:32 UTCVendor advisory
  64. 2026-08-20 03:32 UTCGHSA enrichment
  65. 2026-08-19 17:04 UTCEPSS rescore
  66. 2026-08-19 05:23 UTCEG score recompute
  67. 2026-08-19 05:23 UTCVendor advisory
  68. 2026-08-19 05:23 UTCGHSA enrichment
  69. 2026-08-18 13:48 UTCEPSS rescore
  70. 2026-08-18 07:19 UTCEG score recompute
  71. 2026-08-18 07:19 UTCVendor advisory
  72. 2026-08-18 07:19 UTCGHSA enrichment
  73. 2026-08-17 13:47 UTCEPSS rescore
  74. 2026-08-17 09:20 UTCEG score recompute
  75. 2026-08-17 09:20 UTCVendor advisory

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.