CVE-2024-40965
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.
Does this matter?
Lower severity and a low EPSS score (0.22%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.22% probability · 13th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-667
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/2b42e9587a7a9c7b824e0feb92958f258263963ePatch
- https://git.kernel.org/stable/c/4268254a39484fc11ba991ae148bacbe75d9cc0aPatch
- https://git.kernel.org/stable/c/d038693e08adf9c162c6377800495e4f5a2df045
- https://git.kernel.org/stable/c/2b42e9587a7a9c7b824e0feb92958f258263963ePatch
- https://git.kernel.org/stable/c/4268254a39484fc11ba991ae148bacbe75d9cc0aPatch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.