CVE-2026-80650 json
media: atomisp: gc2235: fix UAF and memory leak
published 2026-08-28 2 mo ago modified 2026-10-30 9 d ago also EUVD-2026-67526
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-80650
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gke Ubuntu 24.04 LTS 6.8.0-1066.74
- linux-gke Ubuntu 26.04 LTS 7.0.0-1008.9
ubuntu advisories UBUNTU-CVE-2026-80650
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654 commit
- git.kernel.org/stable/c/5bed166be3054f9ebb527dbce7158677085eea59 commit
- git.kernel.org/stable/c/592a0e78ab08f6373c40912365759d8a066e7711 commit
- git.kernel.org/stable/c/fdbb8e55578b4ab647fa58827a9dd8730d7f4add commit
- git.kernel.org/stable/c/d57e67ea48e4d095052f2b14d8dd7593621f862f commit
- git.kernel.org/stable/c/f614bf0a64aa1cb7444d152a96798a6bf1d49e1f commit
- git.kernel.org/stable/c/628f763aee0047ff44974388d6f70f75a763026b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80650 updated cvss 5.5
kernel: media: atomisp: gc2235: fix UAF and memory leak
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654
- git.kernel.org /stable/c/5bed166be3054f9ebb527dbce7158677085eea59
- git.kernel.org /stable/c/592a0e78ab08f6373c40912365759d8a066e7711
- git.kernel.org /stable/c/fdbb8e55578b4ab647fa58827a9dd8730d7f4add
- git.kernel.org /stable/c/d57e67ea48e4d095052f2b14d8dd7593621f862f
- git.kernel.org /stable/c/f614bf0a64aa1cb7444d152a96798a6bf1d49e1f
- git.kernel.org /stable/c/628f763aee0047ff44974388d6f70f75a763026b
Sources
- CVE List CVE-2026-80650
- NVD CVE-2026-80650
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.