Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53226: gpio: rockchip: fix generic IRQ chip leak on remove

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1c1e0fc88d6ef65bf15d517853251f75ab9d18c3, 1f34ea5f6114011092d9a5c8b901ad6741144a1d, 50c7a6d2bf179588ba2daee97be93d19c96a94af; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 1c1e0fc88d6ef65bf15d517853251f75ab9d18c3, 1f34ea5f6114011092d9a5c8b901ad6741144a1d, 50c7a6d2bf179588ba2daee97be93d19c96a94af; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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().

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53226

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15 and later · before 6.18.36
  • linux linux kernel6.19 and later · before 7.0.13
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.15affected
    • 936ee2675eee1faca0dcdfa79165c7990422e0fc and later · before 6198123cac2ffd9d9a9d252dfa84ab81fb487ba3affected · git
    • 936ee2675eee1faca0dcdfa79165c7990422e0fc and later · before 50c7a6d2bf179588ba2daee97be93d19c96a94afaffected · git
    • 936ee2675eee1faca0dcdfa79165c7990422e0fc and later · before bace7b99bfa555fe833aee8827b8004c43666d02affected · git
    • 936ee2675eee1faca0dcdfa79165c7990422e0fc and later · before 1f34ea5f6114011092d9a5c8b901ad6741144a1daffected · git
    • 936ee2675eee1faca0dcdfa79165c7990422e0fc and later · before 1c1e0fc88d6ef65bf15d517853251f75ab9d18c3affected · git
    • before 5.15not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
    • 6.12.96 and later · up to and including 6.12.*not affected · semver
    • 6.18.36 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.0.13-17.0.13-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53224Jun 25, 2026 · sctp: validate embedded INIT chunk and address list lengths in cookie
    36Monitor
  • ← EarlierCVE-2026-53225Jun 25, 2026 · sctp: fix uninit-value in __sctp_rcv_asconf_lookup()
    36Monitor
  • Later →CVE-2026-53227Jun 25, 2026 · net: openvswitch: fix possible kfree_skb of ERR_PTR
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1c1e0fc88d6ef65bf15d517853251f75ab9d18c3Vendor (CNA)
Linux Linux1f34ea5f6114011092d9a5c8b901ad6741144a1dVendor (CNA)
Linux Linux50c7a6d2bf179588ba2daee97be93d19c96a94afVendor (CNA)
Linux Linux6198123cac2ffd9d9a9d252dfa84ab81fb487ba3Vendor (CNA)
Linux Linuxbace7b99bfa555fe833aee8827b8004c43666d02Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.96-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records