CVE-2024-53239
ALSA: 6fire: Release resources at card release
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: 6fire: Release resources at card release The current 6fire code tries to release the resources right after the call of usb6fire_chip_abort(). But at this moment, the card object might be still in use (as we're calling snd_card_free_when_closed()). For avoid potential UAFs, move the release of resources to the card's private_free instead of the manual call of usb6fire_chip_destroy() at the USB disconnect callback.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.39
References 9
git.kernel.org
- stable/c/74357d0b5cd3ef544752bc9f21cbeee4902fae6c
- stable/c/273eec23467dfbfbd0e4c10302579ba441fb1e13
- stable/c/f2d06d4e129e2508e356136f99bb20a332ff1a00
- stable/c/b889a7d68d7e76b8795b754a75c91a2d561d5e8c
- stable/c/ea8cc56db659cf0ae57073e32a4735ead7bd7ee3
- stable/c/b754e831a94f82f2593af806741392903f359168
- stable/c/0df7f4b5cc10f5adf98be0845372e9eef7bb5b09
- stable/c/57860a80f03f9dc69a34a5c37b0941ad032a0a8c
- stable/c/a0810c3d6dd2d29a9b92604d682eacd2902ce947