VulnerabilityPublished 28 Oct 2026

CVE-2026-99190: Linux kernel · gpiolib: fix memory leak in gpiod_set_array_value_complex() on error paths

Source GCVE Database

Authoritative record:CVE-2026-99190

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

Data as of 28 Oct 2026, 13:46 UTC

Severity

Low

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

Patch: Available – fixed in c28846ca1ac6134881114d272314623c8433e372, 78189c0e35abbcdab3b8ab0b764d578c02900734, 890c3bf08e0fc09eff788a6cfeded7d21b4d3e9d +1

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-8wj8-f84m-9qv6

What to do

Upgrade Linux kernel to c28846ca1ac6134881114d272314623c8433e372, 78189c0e35abbcdab3b8ab0b764d578c02900734, 890c3bf08e0fc09eff788a6cfeded7d21b4d3e9d or 6.13.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.12.114 <6.13	Fixed in c28846ca1ac6134881114d272314623c8433e372 78189c0e35abbcdab3b8ab0b764d578c02900734 890c3bf08e0fc09eff788a6cfeded7d21b4d3e9d 6.13
LinuxLinux	Affected =6.15	Fixed in–

AI-suggested

A fix for this memory leak has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to ensure the vulnerability is resolved. Since this is a kernel-level fix, no additional mitigation steps are required beyond applying the update.

Description

A memory leak vulnerability was identified and fixed in the Linux kernel's gpiolib subsystem within the function gpiod_set_array_value_complex(). The issue occurs on error paths where allocated bitmaps may not be freed properly after a failed call to gpiochip_set_multiple(), leading to potential memory leakage. Although the error path is unlikely, it is possible and has been addressed by deferring the return code check until after the bitmap is freed.

References

Community reviews

Loading reviews…