First published: Fri Jul 12 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: i2c: lpi2c: Avoid calling clk_get_rate during transfer Instead of repeatedly calling clk_get_rate for each transfer, lock the clock rate and cache the value. A deadlock has been observed while adding tlv320aic32x4 audio codec to the system. When this clock provider adds its clock, the clk mutex is locked already, it needs to access i2c, which in return needs the mutex for clk_get_rate as well.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel | <6.9.7 | 6.9.7 |
redhat/kernel | <6.10 | 6.10 |
Linux Kernel | <6.9.7 | |
debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.133-1 | 6.12.22-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-40965 has been classified as a medium severity vulnerability.
To fix CVE-2024-40965, update to the appropriate kernel versions specified in the remediation details, such as kernel 6.9.7 or kernel 6.10.
CVE-2024-40965 affects specific versions of the Linux kernel across various distributions including Red Hat and Debian.
CVE-2024-40965 is a deadlock vulnerability related to clock rate management in the Linux kernel.
The exploitability of CVE-2024-40965 can depend on specific use cases, but it poses a risk of deadlock during operation.