CVE-2026-80650: Linux kernel · media: atomisp: gc2235: fix UAF and memory leak
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fdbb8e55578b4ab647fa58827a9dd8730d7f4add : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fdbb8e55578b4ab647fa58827a9dd8730d7f4add, f614bf0a64aa1cb7444d152a96798a6bf1d49e1f, d57e67ea48e4d095052f2b14d8dd7593621f862f +3
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Aug 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: media: atomisp: gc2235: fix UAF and memory leak gc2235_probe() handles its error paths incorrectly. If media_entity_pads_init() fails, gc2235_remove() is called, which tears down the subdev and frees dev, but then still falls through to atomisp_register_i2c_module(). This results in use-after-free. If atomisp_register_i2c_module() fails, the media entity and control handler are left initialized and dev is leaked. gc2235_remove() unconditionally calls media_entity_cleanup() and v4l2_ctrl_handler_free(), but these are not initialized at every error path in gc2235_probe(). Replace gc2235_remove() calls in the probe error paths with explicit unwind labels that free only the resources initialized at each point of failure, in reverse order of initialization.
References
- git.kernel.org/stable/c/51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654 (opens in a new tab)
- git.kernel.org/stable/c/592a0e78ab08f6373c40912365759d8a066e7711 (opens in a new tab)
- git.kernel.org/stable/c/fdbb8e55578b4ab647fa58827a9dd8730d7f4add (opens in a new tab)
- git.kernel.org/stable/c/d57e67ea48e4d095052f2b14d8dd7593621f862f (opens in a new tab)
- git.kernel.org/stable/c/f614bf0a64aa1cb7444d152a96798a6bf1d49e1f (opens in a new tab)
- git.kernel.org/stable/c/628f763aee0047ff44974388d6f70f75a763026b (opens in a new tab)