CVE-2024-38618: ALSA: timer: Set lower bound of start tick time
First published: Wed Jun 19 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: ALSA: timer: Set lower bound of start tick time Currently ALSA timer doesn't have the lower limit of the start tick time, and it allows a very small size, e.g. 1 tick with 1ns resolution for hrtimer. Such a situation may lead to an unexpected RCU stall, where the callback repeatedly queuing the expire update, as reported by fuzzer. This patch introduces a sanity check of the timer start tick time, so that the system returns an error when a too small start size is set. As of this patch, the lower limit is hard-coded to 100us, which is small enough but can still work somehow.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <4.19.316 | 4.19.316 |
| redhat/kernel | <5.4.278 | 5.4.278 |
| redhat/kernel | <5.10.219 | 5.10.219 |
| redhat/kernel | <5.15.161 | 5.15.161 |
| redhat/kernel | <6.1.93 | 6.1.93 |
| redhat/kernel | <6.6.33 | 6.6.33 |
| redhat/kernel | <6.9.3 | 6.9.3 |
| redhat/kernel | <6.10 | 6.10 |
| debian/linux | 5.10.223-1 5.10.234-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.16-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/2c95241ac5fc90c929d6c0c023e84bf0d30e84c3
- https://git.kernel.org/stable/c/4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4e
- https://git.kernel.org/stable/c/68396c825c43664b20a3a1ba546844deb2b4e48f
- https://git.kernel.org/stable/c/74bfb8d90f2601718ae203faf45a196844c01fa1
- https://git.kernel.org/stable/c/83f0ba8592b9e258fd80ac6486510ab1dcd7ad6e
- https://git.kernel.org/stable/c/abb1ad69d98cf1ff25bb14fff0e7c3f66239e1cd
- https://git.kernel.org/stable/c/bdd0aa055b8ec7e24bbc19513f3231958741d0ab
- https://git.kernel.org/stable/c/ceab795a67dd28dd942d0d8bba648c6c0f7a044b
- https://launchpad.net/bugs/cve/CVE-2024-38618
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-38618
- https://nvd.nist.gov/vuln/detail/CVE-2024-38618
- https://security-tracker.debian.org/tracker/CVE-2024-38618
- https://ubuntu.com/security/CVE-2024-38618
- https://git.kernel.org/linus/4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4e
- https://access.redhat.com/security/cve/CVE-2024-38618
- https://lore.kernel.org/linux-cve-announce/2024061923-CVE-2024-38618-35a9@gregkh/T
- https://access.redhat.com/errata/RHSA-2024:9315
- https://bugzilla.redhat.com/show_bug.cgi?id=2293329
Frequently Asked Questions
What is the severity of CVE-2024-38618?
CVE-2024-38618 is classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-38618?
To fix CVE-2024-38618, update the Linux kernel to versions 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.3, or 6.10 as per the advisories.
What versions of the Linux kernel are affected by CVE-2024-38618?
The affected versions of the Linux kernel are prior to 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.3, and 6.10.
What component is impacted by CVE-2024-38618?
CVE-2024-38618 impacts the ALSA timer component of the Linux kernel.
Is there a workaround for CVE-2024-38618?
There are currently no known workarounds for CVE-2024-38618, and patching is the recommended approach.
- agent/title
- agent/type
- collector/launchpad-cve
- source/Launchpad
- agent/remedy
- agent/author
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-38618
- agent/software-canonical-lookup
- agent/references
- agent/severity
- collector/nvd-cve
- agent/description
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- package-manager/redhat
- package-manager/debian