# CVE-2026-99161: i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111302, BELL-CVE-2026-99161, DEBIAN-CVE-2026-99161, GHSA-2mrq-r7cq-whw5, UBUNTU-CVE-2026-99161

## What is CVE-2026-99161?

CVE-2026-99161 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()

In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any
subsequent operation fails or when the module is unloaded, the clock
reference count is never decremented via clk_put(), leading to a
resource leak.

Switch to devm_clk_get() so that the clock is automatically managed
and released.

## Which versions are affected by CVE-2026-99161?


## How do I fix CVE-2026-99161?

Upgrade to a fixed version.

## Is CVE-2026-99161 being exploited?

There is no known exploitation of CVE-2026-99161 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99161 and fix it if it is affected.

What it is: CVE-2026-99161 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99161 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99161/ (Markdown: https://insights.sbomify.com/CVE-2026-99161/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99161
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99161
- OSV: https://osv.dev/vulnerability/CVE-2026-99161

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99161/
Summaries are generated and may contain mistakes; the official description above is the record.