Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80650media: atomisp: gc2235: fix UAF and memory leak

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected a49d25364dfb9f8a64037488a39ab1f56c5fa419 – < 51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654
    • affected ad85094b293e40e7a2f831b0311a389d952ebd5e – < 5bed166be3054f9ebb527dbce7158677085eea59
    • affected ad85094b293e40e7a2f831b0311a389d952ebd5e – < 592a0e78ab08f6373c40912365759d8a066e7711
    • affected ad85094b293e40e7a2f831b0311a389d952ebd5e – < fdbb8e55578b4ab647fa58827a9dd8730d7f4add
    • affected ad85094b293e40e7a2f831b0311a389d952ebd5e – < d57e67ea48e4d095052f2b14d8dd7593621f862f
    • affected ad85094b293e40e7a2f831b0311a389d952ebd5e – < f614bf0a64aa1cb7444d152a96798a6bf1d49e1f
    • affected ad85094b293e40e7a2f831b0311a389d952ebd5e – < 628f763aee0047ff44974388d6f70f75a763026b
  • Linux · Linux

    • affected 4.12
    • affected 5.8
    • unaffected < 4.12
    • unaffected 4.18 – < 5.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80650 badge
[![CVE-2026-80650](https://cveledger.app/badge/CVE-2026-80650.svg)](https://cveledger.app/cve/CVE-2026-80650)

Record last updated .