CVE-2023-53579

Q: What is the severity of CVE-2023-53579?

CVE-2023-53579 has a CVSS score of 5.5 (MEDIUM). This CVE describes a resource leak vulnerability in the Linux kernel's mvebu GPIO driver where an interrupt request (irq) domain isn't properly released during driver detach. This affects Linux systems using the mvebu GPIO driver, potentially leading to resource exhaustion over time. The vulnerability requires local access to trigger.

5.5 MEDIUM

📋 TL;DR

This CVE describes a resource leak vulnerability in the Linux kernel's mvebu GPIO driver where an interrupt request (irq) domain isn't properly released during driver detach. This affects Linux systems using the mvebu GPIO driver, potentially leading to resource exhaustion over time. The vulnerability requires local access to trigger.

💻 Affected Systems

Products:

Linux kernel with mvebu GPIO driver

Versions: Linux kernel versions before the fix commits (specific versions vary by distribution)

Operating Systems: Linux distributions using affected kernel versions

Default Config Vulnerable: ⚠️ Yes

Notes: Only affects systems using the mvebu GPIO driver, typically found on Marvell Armada platforms. The vulnerability triggers specifically during driver detach events.

📦 What is this software?

Linux Kernel by Linux

The Linux Kernel is the core component of the Linux operating system, serving as the critical interface between computer hardware and software processes. As the heart of millions of servers, cloud infrastructure, embedded systems, Android devices, and IoT deployments worldwide, the Linux Kernel mana...

Learn more about Linux Kernel →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Repeated driver detach/attach cycles could exhaust kernel resources, leading to system instability, denial of service, or kernel panic.

🟠

Likely Case

Gradual resource leakage during normal driver operations, potentially causing system performance degradation or instability over extended periods.

🟢

If Mitigated

Minimal impact with proper monitoring and resource limits in place, though resource leakage still occurs.

🌐 Internet-Facing: LOW - Requires local access to trigger, not directly exploitable over network.

🏢 Internal Only: MEDIUM - Local users or processes could potentially trigger the resource leak, affecting system stability.

🎯 Exploit Status

Public PoC: ✅ No

Weaponized: NO

Unauthenticated Exploit: ✅ No

Complexity: MEDIUM

Exploitation requires local access and ability to trigger driver detach events. No known public exploits exist.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Fixed in kernel commits: 44e2afbf650f, 644ee70267a9, b19e90521286, d9b791d83623

Vendor Advisory: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

Restart Required: Yes

Instructions:

1. Update Linux kernel to version containing the fix commits. 2. Check distribution-specific security advisories. 3. Reboot system to load patched kernel.

🔧 Temporary Workarounds

Disable mvebu GPIO driver

linux

Prevent loading of vulnerable driver module

echo 'blacklist gpio-mvebu' >> /etc/modprobe.d/blacklist.conf
rmmod gpio-mvebu

🧯 If You Can't Patch

Monitor system resources (memory, IRQ domains) for unusual consumption patterns
Restrict local user access to systems using mvebu GPIO driver

🔍 How to Verify

Check if Vulnerable:

Check kernel version and if mvebu GPIO driver is loaded: 'uname -r' and 'lsmod | grep gpio_mvebu'

Check Version:

uname -r

Verify Fix Applied:

Verify kernel version includes fix commits or check with 'modinfo gpio_mvebu' for version details

📡 Detection & Monitoring

Log Indicators:

Kernel messages about resource exhaustion
GPIO driver detach events without proper cleanup

Network Indicators:

None - local vulnerability only

SIEM Query:

source="kernel" AND ("resource" OR "exhaustion" OR "mvebu" OR "gpio")

📊 Metadata

CVE ID: CVE-2023-53579

CVSS v3 Score: 5.5 (MEDIUM)

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

CWE: CWE-401

EPSS Score: 0.02% exploit probability (5.3th percentile)

Published: October 4, 2025

Last Updated: February 10, 2026

📋 TL;DR

💻 Affected Systems

📦 What is this software?

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

Linux Kernel by Linux

⚠️ Risk & Real-World Impact

Worst Case

Likely Case

If Mitigated

🎯 Exploit Status

🛠️ Fix & Mitigation

✅ Official Fix

Instructions:

🔧 Temporary Workarounds

Disable mvebu GPIO driver

🧯 If You Can't Patch

🔍 How to Verify

Check if Vulnerable:

Check Version:

Verify Fix Applied:

📡 Detection & Monitoring

Log Indicators:

Network Indicators:

SIEM Query:

📊 Metadata

🔗 References

📤 Share & Export

🔗 Related Vulnerabilities