CVE-2026-74463

CVE CVE-2026-74463EUVD EUVD-2026-59656Veröffentlicht 2026-08-15T12:27:03.000ZZuletzt geändert 2026-08-19T16:37:02.000Z

Was das Advisory beschreibt

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 'prepare_lock' mutex and the driver calls i2c_transfer() to update the client's chip registers, stalling for the adapter'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's input clock to calculate bus timings. This call attempts to acquire the blocked CCF 'prepare_lock', 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 internal locks without any risk of stale timings. Assisted-by web based Google AI (pinpointing the bug and writing the message).

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux ba92222ed63a12d09120df9b92f56cc990abac19 <aa1944b52d6492c48bdd17046578aa0d953546e6; ba92222ed63a12d09120df9b92f56cc990abac19 <19b783335d62e7a2367436a6e1f1b37da1878360; patch: 6.12.103; patch: 5.15.216; ba92222ed63a12d09120df9b92f56cc990abac19 <d99607c888f26e8a4e9fe9772860cef4aff86bb4; ba92222ed63a12d09120df9b92f56cc990abac19 <f96a719d9f8a797105ec5cacf568ab128e33391f; 4.1; patch: 7.2; ba92222ed63a12d09120df9b92f56cc990abac19 <deffad5bb4f8b4f09e46252f24754ddc9960b244; patch: 5.10.265; patch: 6.6.151; patch: 7.1.8; ba92222ed63a12d09120df9b92f56cc990abac19 <cc111696ef420f6bb552b2526530067977f0b406; patch: 0; ba92222ed63a12d09120df9b92f56cc990abac19 <14429dc1c756c35e106f01ff09cadccb82f5531d; ba92222ed63a12d09120df9b92f56cc990abac19 <b6cb47e186abba85a3b08aa3023067ab82577286; patch: 6.18.44; patch: 6.1.183

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.