https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 07:57:38 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64236 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: davinci: fix division by zero on missing clock-frequency</p> <p>When the &#39;clock-frequency&#39; 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.</p> <p>The probe function divided the fallback value by 1000, causing integer truncation that resulted in dev-&gt;bus_freq = 0. This triggered a deterministic division-by-zero kernel panic when calculating clock dividers later in the probe sequence.</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: davinci: fix division by zero on missing clock-frequency</p> <p>When the &#39;clock-frequency&#39; 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.</p> <p>The probe function divided the fallback value by 1000, causing integer truncation that resulted in dev-&gt;bus_freq = 0. This triggered a deterministic division-by-zero kernel panic when calculating clock dividers later in the probe sequence.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-64236