CVE-2026-72324: gpio: mvebu: free generic chips on unbind

Published Aug 15, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved:

gpio: mvebu: free generic chips on unbind

irqallocdomaingenericchips() allocates generic chip data that must be freed via irqdomainremovegenericchips(). The devres action mvebugpioremoveirqdomain() only called irqdomainremove(), which only frees the generic chips if IRQDOMAINFLAGDESTROYGC is set. Call irqdomainremovegenericchips() explicitly before irqdomainremove() instead.

Event History

Aug 15, 2026

CVE Published

via MITRE·05:55 AM

Data Sourced

via MITRE·05:55 AM

Description

Frequently Asked Questions

What is the severity of CVE-2026-72324?

CVE-2026-72324 has a risk rating of 17, indicating a significant potential impact.

How do I fix CVE-2026-72324?

To fix CVE-2026-72324, ensure that irq_domain_remove_generic_chips() is called appropriately in your code.

What systems are affected by CVE-2026-72324?

CVE-2026-72324 affects the Linux kernel versions where the mvebu GPIO handling is implemented.

Is CVE-2026-72324 remotely exploitable?

The details do not specify remote exploitability, but vulnerabilities in the kernel typically have a heightened risk profile.

When was CVE-2026-72324 published?

CVE-2026-72324 was published on August 15, 2026.

CVE-2026-72324: gpio: mvebu: free generic chips on unbind

Event History

Don't miss critical vulnerabilities

Frequently Asked Questions

What is the severity of CVE-2026-72324?

How do I fix CVE-2026-72324?

What systems are affected by CVE-2026-72324?

Is CVE-2026-72324 remotely exploitable?

When was CVE-2026-72324 published?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2026-72324?

How do I fix CVE-2026-72324?

What systems are affected by CVE-2026-72324?

Is CVE-2026-72324 remotely exploitable?

When was CVE-2026-72324 published?