CVE-2026-64461

PCI: mediatek: Fix IRQ domain leak when port fails to enable

N/A
Published: July 25, 2026 at 08:51 AM UTC
Updated: August 17, 2026 at 05:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: PCI: mediatek: Fix IRQ domain leak when port fails to enable When mtk_pcie_enable_port() fails, mtk_pcie_port_free() removes the port from pcie->ports and frees the port structure. However, the IRQ domains set up earlier by mtk_pcie_init_irq_domain() are never freed. Fix this by refactoring mtk_pcie_irq_teardown() into a per-port helper, mtk_pcie_irq_teardown_port(), and calling it from mtk_pcie_setup() when mtk_pcie_enable_port() fails. Since the IRQ teardown must only happen in the probe error path (during resume, child devices may have active MSI mappings and the NOIRQ context prohibits sleeping locks), mtk_pcie_enable_port() is changed to return an error code so callers can distinguish the two paths and act accordingly. This issue was reported by Sashiko while reviewing the EcoNet EN7528 SoC support series.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14 ≤ v < 5.10.2614.14 ≤ v < 5.15.2124.14 ≤ v < 6.1.1784.14 ≤ v < 6.12.974.14 ≤ v < 6.18.394.14 ≤ v < 6.6.1454.14 ≤ v < 7.1.44.14 ≤ v < 7.24.14b099631df160ec608cd6147f4d20a8042567a5b8
Vendor states this is fixed in 1fbe8972a39548a633d06d7b03a01b7b119a2c12 (fixed)
Vendor states this is fixed in 6e6a529d6f779413379b4404c9ef6a36c0337225 (fixed)
Vendor states this is fixed in ce52e494a7555bdae1d990a2654fd7547ef6d986 (fixed)
Vendor states this is fixed in df77314b3bedbd9ad5d6f0682f98b99e3c5f7e2e (fixed)
Vendor states this is fixed in e23da72ef202654a7d5269885c4fa39a8404db76 (fixed)
Vendor states this is fixed in ec7c05eed47d8b15c45380aee7ca168a82e15035 (fixed)
Vendor states this is fixed in f865a57896bd92d7662eb2818d8f48872e2cbbc7 (fixed)
Vendor states this is fixed in fe8c701a53c2816cd82301f66c671d952003c1b0 (fixed)
Vendor states this is fixed in 4.14 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card