VulnerabilityPublished 28 Oct 2026

CVE-2026-99161: Linux kernel · i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()

Source GCVE Database

Authoritative record:CVE-2026-99161

Not known to be exploited · fixed in aaabefc79b0ff0018e8e3832169bbe359d0551fc : update Linux kernel when convenient.

Data as of 28 Oct 2026, 13:58 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in aaabefc79b0ff0018e8e3832169bbe359d0551fc, 1875de656370c89b99a150d220df876288ee0344, 5d476bb76b7d72d8b7ed04a9c614900b097e3af7

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-2mrq-r7cq-whw5

What to do

Upgrade Linux kernel to aaabefc79b0ff0018e8e3832169bbe359d0551fc, 1875de656370c89b99a150d220df876288ee0344 or 5d476bb76b7d72d8b7ed04a9c614900b097e3af7.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 560746eb79d3124a278452c8dd968682b521cc82, < aaabefc79b0ff0018e8e3832169bbe359d0551fc	Fixed in aaabefc79b0ff0018e8e3832169bbe359d0551fc
LinuxLinux	Affected ≥ 560746eb79d3124a278452c8dd968682b521cc82, < 1875de656370c89b99a150d220df876288ee0344	Fixed in 1875de656370c89b99a150d220df876288ee0344
LinuxLinux	Affected ≥ 560746eb79d3124a278452c8dd968682b521cc82, < 5d476bb76b7d72d8b7ed04a9c614900b097e3af7	Fixed in 5d476bb76b7d72d8b7ed04a9c614900b097e3af7
LinuxLinux	Affected =3.11	Fixed in–
Linuxlinux/kernel`pkg:deb/linux/kernel`Other threats	Affected =3.11	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that replaces manual clock management with devm_clk_get(), which automatically handles clock resource release. Users should apply the updated Linux kernel version containing this fix to remediate the issue.

Description

A resource leak vulnerability was fixed in the Linux kernel's viai2c-wmt driver. The issue involved the clock reference count not being decremented properly when errors occurred or the module was unloaded, due to improper management of the clock resource in wmt_i2c_probe().

References

Community reviews

Loading reviews…