UBUNTU-CVE-2026-99161: Medium severity ubuntu/linux vulnerability
In the Linux kernel, the following vulnerability has been resolved: i2c: viai2c-wmt: Fix clock leak in wmti2cprobe() In wmti2cprobe(), i2c->clk is acquired using ofclkget(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clkput(), leading to a resource leak. Switch to devmclkget() so that the clock is automatically managed and released.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernel i2c viai2c-wmtto a version that resolves this vulnerability.Patch i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue affects Ubuntu kernel packages listed as linux, linux-fips, linux-aws, linux-azure, linux-gcp, linux-oracle, linux-aws-fips, and linux-azure-fips when the viai2c-wmt driver is used.
What conditions trigger the resource leak?
The leak occurs when wmt_i2c_probe() obtains its clock and a later probe operation fails, or when the driver module is unloaded. In those cases, the acquired clock reference is not released.
Is this an externally exploitable vulnerability?
The provided information describes a kernel driver clock-reference resource leak. It does not state that an unprivileged or remote attacker can trigger it, nor does it provide an exploitation path.
What is the remediation?
The resolved implementation uses devm_clk_get() instead of of_clk_get(), allowing the device-managed clock reference to be released automatically.