CVE-2024-36973: misc: microchip: pci1xxxx: fix double free in the error handling of gp_aux_bus_probe()
In the Linux kernel, the following vulnerability has been resolved:
misc: microchip: pci1xxxx: fix double free in the error handling of gp_aux_bus_probe()
When auxiliary_device_add() returns error and then calls
auxiliary_device_uninit(), callback function
gp_auxiliary_device_release() calls ida_free() and
kfree(aux_device_wrapper) to free memory. We should't
call them again in the error handling path.
Fix this by skipping the redundant cleanup functions.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel double-free bug in the Microchip pci1xxxx auxiliary bus probe error path. It is not reported as actively exploited and has no CVSS score in the provided sources. Business urgency is highest for Linux systems that use this driver or related hardware; otherwise it should be handled through normal kernel patch management.
Executive priority
Treat as a targeted kernel maintenance issue, not an internet-wide emergency based on current evidence. Patch affected Linux fleets through the normal urgent kernel update process, with faster attention for systems using the Microchip pci1xxxx driver.
Technical view
The flaw occurs when auxiliary_device_add() fails and triggers auxiliary_device_uninit(); the release callback already frees the IDA entry and wrapper memory. The vulnerable error path then performs redundant cleanup, creating a double-free condition. Stable kernel commits fix this by skipping the duplicate cleanup functions.
Likely exposure
Exposure appears limited to Linux kernels containing the affected Microchip pci1xxxx driver path, especially systems with relevant hardware or enabled driver support. The provided data lists Linux 6.1-era through fixed stable releases, but does not provide distribution-specific package coverage beyond the Debian LTS reference.
Exploitation context
The source bundle does not show active exploitation, KEV listing, public exploit availability, or practical attack requirements. The bug is in kernel error handling during device probe, so impact depends on whether an attacker can influence that failure path in a relevant environment.
Researcher notes
Key unknowns are practical exploitability, required local privileges, and reachable failure conditions. The provided record identifies a double-free fix but does not include CVSS, CWE, exploit evidence, or a complete distro-by-distro affected package matrix.
Mitigation direction
Apply vendor or distribution kernel updates containing the stable fixes.
Prioritize systems using Microchip PCI1xxxx hardware or the pci1xxxx driver.
Review Debian LTS guidance where Debian systems are in scope.
If no update is available, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across affected systems.
Check whether the pci1xxxx driver or related hardware is present.
Confirm kernel changelogs include one of the referenced stable fix commits.
Track distribution advisories for package-specific fixed versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-36973 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.