https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 16:07:52 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-74463 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-74463 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090 certfr-2026-avi-1090 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090 https://cve.radiocsirt.org/vuln/euvd-2026-356379 EUVD-2026-356379 https://cve.radiocsirt.org/vuln/euvd-2026-356379 https://cve.radiocsirt.org/vuln/fkie_cve-2026-74463 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock</p> <p>Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF.</p> <p>During an i2c client clock (generator) frequency change, the CCF acquires its global &#39;prepare_lock&#39; mutex and the driver calls i2c_transfer() to update the client&#39;s chip registers, stalling for the adapter&#39;s I2C bus lock.</p> <p>Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller&#39;s input clock to calculate bus timings. This call attempts to acquire the blocked CCF &#39;prepare_lock&#39;, creating a circular dependency that freezes the system.</p> <p>The jz4780 host controller clock itself is static and never changes at runtime.</p> <p>However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks.</p> <p>Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from t…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock</p> <p>Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF.</p> <p>During an i2c client clock (generator) frequency change, the CCF acquires its global &#39;prepare_lock&#39; mutex and the driver calls i2c_transfer() to update the client&#39;s chip registers, stalling for the adapter&#39;s I2C bus lock.</p> <p>Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller&#39;s input clock to calculate bus timings. This call attempts to acquire the blocked CCF &#39;prepare_lock&#39;, creating a circular dependency that freezes the system.</p> <p>The jz4780 host controller clock itself is static and never changes at runtime.</p> <p>However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks.</p> <p>Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from t…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-74463 https://cve.radiocsirt.org/vuln/ghsa-2xgc-rc56-qqm7 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock</p> <p>Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF.</p> <p>During an i2c client clock (generator) frequency change, the CCF acquires its global &#39;prepare_lock&#39; mutex and the driver calls i2c_transfer() to update the client&#39;s chip registers, stalling for the adapter&#39;s I2C bus lock.</p> <p>Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller&#39;s input clock to calculate bus timings. This call attempts to acquire the blocked CCF &#39;prepare_lock&#39;, creating a circular dependency that freezes the system.</p> <p>The jz4780 host controller clock itself is static and never changes at runtime.</p> <p>However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks.</p> <p>Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from t…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock</p> <p>Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF.</p> <p>During an i2c client clock (generator) frequency change, the CCF acquires its global &#39;prepare_lock&#39; mutex and the driver calls i2c_transfer() to update the client&#39;s chip registers, stalling for the adapter&#39;s I2C bus lock.</p> <p>Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller&#39;s input clock to calculate bus timings. This call attempts to acquire the blocked CCF &#39;prepare_lock&#39;, creating a circular dependency that freezes the system.</p> <p>The jz4780 host controller clock itself is static and never changes at runtime.</p> <p>However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks.</p> <p>Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from t…</p> https://cve.radiocsirt.org/vuln/ghsa-2xgc-rc56-qqm7 https://cve.radiocsirt.org/vuln/msrc_cve-2026-74463 msrc_CVE-2026-74463 https://cve.radiocsirt.org/vuln/msrc_cve-2026-74463 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74463 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF. During an i2c client clock (generator) frequency change, the CCF acquires its global &#39;prepare_lock&#39; mutex and the driver calls i2c_transfer() to update the client&#39;s chip registers, stalling for the adapter&#39;s I2C bus lock. Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller&#39;s input clock to calculate bus timings. This call attempts to acquire the blocked CCF &#39;prepare_lock&#39;, creating a circular dependency that freezes the system. The jz4780 host controller clock itself is static and never changes at runtime. However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks. Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from the CCF…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock Fix a severe AB/BA deadlock between the Common Clock Framework (CCF) and the I2C adapter lock, which triggers when an I2C-controlled clock generator client (like the Si5351) is registered or modified under the CCF. During an i2c client clock (generator) frequency change, the CCF acquires its global &#39;prepare_lock&#39; mutex and the driver calls i2c_transfer() to update the client&#39;s chip registers, stalling for the adapter&#39;s I2C bus lock. Concurrently, an independent, parallel transfer on the same bus (e.g., a GPIO expander handling LEDs) can hold the I2C adapter lock. Inside this parallel transfer path, jz4780_i2c_set_speed() calls clk_get_rate() on the host controller&#39;s input clock to calculate bus timings. This call attempts to acquire the blocked CCF &#39;prepare_lock&#39;, creating a circular dependency that freezes the system. The jz4780 host controller clock itself is static and never changes at runtime. However, calling clk_get_rate() inside the active transfer path introduces an unnecessary dependency on the CCF internal locks. Eliminate this synchronous clk_get_rate() call from the active transfer path by caching the static host peripheral clock rate once - inside the private jz4780_i2c structure during jz4780_i2c_probe(). Update jz4780_i2c_set_speed() to use this cached value, safely decoupling active I2C transactions from the CCF…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74463 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852