CVE-2024-38618: ALSA: timer: Set lower bound of start tick time
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.64% (FIRST EPSS); higher than 51% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2c95241ac5fc90c929d6c0c023e84bf0d30e84c3, 4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4e, 68396c825c43664b20a3a1ba546844deb2b4e48f.
Low priority for now. Upgrade to Linux Linux 2c95241ac5fc90c929d6c0c023e84bf0d30e84c3, 4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4e, 68396c825c43664b20a3a1ba546844deb2b4e48f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.316
- linux linux kernel4.20 and later · before 5.4.278
- linux linux kernel5.5 and later · before 5.10.219
- linux linux kernel5.11 and later · before 5.15.161
- linux linux kernel5.16 and later · before 6.1.93
- linux linux kernel6.2 and later · before 6.6.33
- linux linux kernel6.7 and later · before 6.9.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.29affected
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before 68396c825c43664b20a3a1ba546844deb2b4e48faffected · git
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before 74bfb8d90f2601718ae203faf45a196844c01fa1affected · git
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before bdd0aa055b8ec7e24bbc19513f3231958741d0abaffected · git
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before 83f0ba8592b9e258fd80ac6486510ab1dcd7ad6eaffected · git
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before ceab795a67dd28dd942d0d8bba648c6c0f7a044baffected · git
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before 2c95241ac5fc90c929d6c0c023e84bf0d30e84c3affected · git
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before abb1ad69d98cf1ff25bb14fff0e7c3f66239e1cdaffected · git
- bbaf5e97337287479eb78dbc3822d9560bbfd2e2 and later · before 4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4eaffected · git
- before 2.6.29not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.94-1 | 6.1.94-1 |
| Debian:13 | linux | before 6.9.7-1 | 6.9.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-38616Jun 19, 2024 · wifi: carl9170: re-fix fortified-memset warning32Monitor
- ← EarlierCVE-2024-38617Jun 19, 2024 · kunit/fortify: Fix mismatched kvalloc()/vfree() usage22Monitor
- Later →CVE-2021-47576Jun 19, 2024 · scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2c95241ac5fc90c929d6c0c023e84bf0d30e84c3 | Vendor (CNA) |
| Linux Linux | 4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4e | Vendor (CNA) |
| Linux Linux | 68396c825c43664b20a3a1ba546844deb2b4e48f | Vendor (CNA) |
| Linux Linux | 74bfb8d90f2601718ae203faf45a196844c01fa1 | Vendor (CNA) |
| Linux Linux | 83f0ba8592b9e258fd80ac6486510ab1dcd7ad6e | Vendor (CNA) |
| Linux Linux | abb1ad69d98cf1ff25bb14fff0e7c3f66239e1cd | Vendor (CNA) |
| Linux Linux | bdd0aa055b8ec7e24bbc19513f3231958741d0ab | Vendor (CNA) |
| Linux Linux | ceab795a67dd28dd942d0d8bba648c6c0f7a044b | Vendor (CNA) |
| debian:linux | 6.1.94-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/4a63bd179fa8d3fcc44a0d9d71d941ddd62f0c4e
- git.kernel.org/stable/c/68396c825c43664b20a3a1ba546844deb2b4e48f
- git.kernel.org/stable/c/74bfb8d90f2601718ae203faf45a196844c01fa1
- git.kernel.org/stable/c/83f0ba8592b9e258fd80ac6486510ab1dcd7ad6e
- git.kernel.org/stable/c/abb1ad69d98cf1ff25bb14fff0e7c3f66239e1cd
- git.kernel.org/stable/c/bdd0aa055b8ec7e24bbc19513f3231958741d0ab
- git.kernel.org/stable/c/ceab795a67dd28dd942d0d8bba648c6c0f7a044b
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.