ALSA: pcm: Fix races among concurrent hw_params and hw_free calls
Noroxi assessment
Priority: Monitor (action score 31/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.30% (FIRST EPSS).
- 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 0090c13cbbdffd7da079ac56f80373a9a1be0bf8, 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8, 1bbf82d9f961414d6c76a08f7f843ea068e0ab7b.
Low priority for now. Upgrade to Linux Linux 0090c13cbbdffd7da079ac56f80373a9a1be0bf8, 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8, 1bbf82d9f961414d6c76a08f7f843ea068e0ab7b 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: pcm: Fix races among concurrent hw_params and hw_free calls Currently we have neither proper check nor protection against the concurrent calls of PCM hw_params and hw_free ioctls, which may result in a UAF. Since the existing PCM stream lock can't be used for protecting the whole ioctl operations, we need a new mutex to protect those racy calls. This patch introduced a new mutex, runtime->buffer_mutex, and applies it to both hw_params and hw_free ioctl code paths. Along with it, the both functions are slightly modified (the mmap_count check is moved into the state-check block) for code simplicity.
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.14.279
- linux linux kernel4.15 and later · before 4.19.243
- linux linux kernel4.20 and later · before 5.4.193
- linux linux kernel5.5 and later · before 5.10.109
- linux linux kernel5.11 and later · before 5.15.32
- linux linux kernel5.16 and later · before 5.16.18
- linux linux kernel5.17 and later · before 5.17.1
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.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a42aa926843acca96c0dfbde2e835b8137f2f092affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9cb6c40a6ebe4a0cfc9d6a181958211682cffea9affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fbeb492694ce0441053de57699e1e2b7bc148a69affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 33061d0fba51d2bf70a2ef9645f703c33fe8e438affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0090c13cbbdffd7da079ac56f80373a9a1be0bf8affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1bbf82d9f961414d6c76a08f7f843ea068e0ab7baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 92ee3c60ec9fe64404dc035e7c41277d74aa26cbaffected · git
- before 2.6.12not 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 5.17.3-1 | 5.17.3-1 |
| Red Hat:rhel_aus:8.6::baseos | bpftool | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | bpftool-debuginfo | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-abi-stablelists | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-core | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debug | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debug-core | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debug-debuginfo | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debug-devel | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debug-modules | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debug-modules-extra | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debuginfo | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-devel | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-doc | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-modules | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-modules-extra | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-tools | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-tools-debuginfo | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | kernel-tools-libs | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | perf | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | perf-debuginfo | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
| Red Hat:rhel_aus:8.6::baseos | python3-perf | before 0:4.18.0-372.109.1.el8_6 | 0:4.18.0-372.109.1.el8_6 |
+17
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49289Feb 26, 2025 · uaccess: fix integer overflow on access_ok()28Monitor
- ← EarlierCVE-2022-49290Feb 26, 2025 · mac80211: fix potential double free on mesh join31Monitor
- Later →CVE-2022-49292Feb 26, 2025 · ALSA: oss: Fix PCM OSS buffer allocation overflow31Monitor
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 | 0090c13cbbdffd7da079ac56f80373a9a1be0bf8 | Vendor (CNA) |
| Linux Linux | 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8 | Vendor (CNA) |
| Linux Linux | 1bbf82d9f961414d6c76a08f7f843ea068e0ab7b | Vendor (CNA) |
| Linux Linux | 33061d0fba51d2bf70a2ef9645f703c33fe8e438 | Vendor (CNA) |
| Linux Linux | 92ee3c60ec9fe64404dc035e7c41277d74aa26cb | Vendor (CNA) |
| Linux Linux | 9cb6c40a6ebe4a0cfc9d6a181958211682cffea9 | Vendor (CNA) |
| Linux Linux | a42aa926843acca96c0dfbde2e835b8137f2f092 | Vendor (CNA) |
| Linux Linux | fbeb492694ce0441053de57699e1e2b7bc148a69 | Vendor (CNA) |
| debian:linux | 5.17.3-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-372.109.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| suse:kernel-default | 3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-docs | 3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-ec2 | 3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-source | 3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-syms | 3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-trace | 3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-xen | 3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (7 more)Show less
- git.kernel.org/stable/c/0f6947f5f5208f6ebd4d76a82a4757e2839a23f8
- git.kernel.org/stable/c/1bbf82d9f961414d6c76a08f7f843ea068e0ab7b
- git.kernel.org/stable/c/33061d0fba51d2bf70a2ef9645f703c33fe8e438
- git.kernel.org/stable/c/92ee3c60ec9fe64404dc035e7c41277d74aa26cb
- git.kernel.org/stable/c/9cb6c40a6ebe4a0cfc9d6a181958211682cffea9
- git.kernel.org/stable/c/a42aa926843acca96c0dfbde2e835b8137f2f092
- git.kernel.org/stable/c/fbeb492694ce0441053de57699e1e2b7bc148a69
Vendor advisories and official records. Exploit/PoC links are deliberately left out.