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-53226gpio: rockchip: fix generic IRQ chip leak on remove

Description

In the Linux kernel, the following vulnerability has been resolved: gpio: rockchip: fix generic IRQ chip leak on remove The driver allocates domain generic chips using irq_alloc_domain_generic_chips() during probe. However, on driver remove/teardown, the generic chips are not automatically freed when the IRQ domain is removed because the domain flags do not include IRQ_DOMAIN_FLAG_DESTROY_GC. This causes both the domain generic chips structure and the associated generic chips to be leaked. Additionally, the generic chips remain on the global gc_list and may later be visited by generic IRQ chip suspend, resume, or shutdown callbacks after the GPIO bank has been removed, potentially resulting in a use-after-free and kernel crash. Fix the resource leak by explicitly calling irq_domain_remove_generic_chips() before removing the IRQ domain in rockchip_gpio_remove().

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 4 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

CVSS scores of CVE-2026-53226, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 936ee2675eee1faca0dcdfa79165c7990422e0fc – < 6198123cac2ffd9d9a9d252dfa84ab81fb487ba3
    • affected 936ee2675eee1faca0dcdfa79165c7990422e0fc – < 50c7a6d2bf179588ba2daee97be93d19c96a94af
    • affected 936ee2675eee1faca0dcdfa79165c7990422e0fc – < bace7b99bfa555fe833aee8827b8004c43666d02
    • affected 936ee2675eee1faca0dcdfa79165c7990422e0fc – < 1f34ea5f6114011092d9a5c8b901ad6741144a1d
    • affected 936ee2675eee1faca0dcdfa79165c7990422e0fc – < 1c1e0fc88d6ef65bf15d517853251f75ab9d18c3
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .