CVE-2024-38605
Last modified
CVE-2024-38605 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. EPSS estimates a 1.09% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.9, < 5.10.219 |
| Linux | Linux Kernel | >= 5.11, < 5.15.161 |
| Linux | Linux Kernel | >= 5.16, < 6.1.93 |
| Linux | Linux Kernel | >= 6.2, < 6.6.33 |
| Linux | Linux Kernel | >= 6.7, < 6.8.12 |
| Linux | Linux Kernel | >= 6.9, < 6.9.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-38605?
How severe is CVE-2024-38605?
How do I fix CVE-2024-38605?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-3860An out-of-memory condition during object initialization coul…6.2
- CVE-2024-38600In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38601In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-38602In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38603In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38604In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38606In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-38607In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38608In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38609In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-3861If an AlignedBuffer were assigned to itself, the subsequent …4
- CVE-2024-38610In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2024-38605?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
