CVE-2022-49288: ALSA: pcm: Fix races among concurrent prealloc proc writes
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.28% (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 37b12c16beb6f6c1c3c678c1aacbc46525c250f7, 51fce708ab8986a9879ee5da946a2cc120f1036d, 5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6.
Low priority for now. Upgrade to Linux Linux 37b12c16beb6f6c1c3c678c1aacbc46525c250f7, 51fce708ab8986a9879ee5da946a2cc120f1036d, 5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6 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 prealloc proc writes We have no protection against concurrent PCM buffer preallocation changes via proc files, and it may potentially lead to UAF or some weird problem. This patch applies the PCM open_mutex to the proc write operation for avoiding the racy proc writes and the PCM stream open (and further operations).
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th 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.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
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.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 e7786c445bb67a9a6e64f66ebd6b7215b153ff7daffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e14dca613e0a6ddc2bf6e360f16936a9f865205baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 37b12c16beb6f6c1c3c678c1aacbc46525c250f7affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b560d670c87d7d40b3cf6949246fa4c7aa65a00aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 51fce708ab8986a9879ee5da946a2cc120f1036daffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a21d2f323b5a978dedf9ff1d50f101f85e39b3f2affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 69534c48ba8ce552ce383b3dfdb271ffe51820c3affected · 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 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-default | before 3.0.101-108.180.1 | 3.0.101-108.180.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-docs | before 3.0.101-108.180.1 | 3.0.101-108.180.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-ec2 | before 3.0.101-108.180.1 | 3.0.101-108.180.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-source | before 3.0.101-108.180.1 | 3.0.101-108.180.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-syms | before 3.0.101-108.180.1 | 3.0.101-108.180.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-trace | before 3.0.101-108.180.1 | 3.0.101-108.180.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-xen | before 3.0.101-108.180.1 | 3.0.101-108.180.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-2022-49286Feb 26, 2025 · tpm: use try_get_ops() in tpm-space.c18Monitor
- ← EarlierCVE-2022-49287Feb 26, 2025 · tpm: fix reference counting for struct tpm_chip28Monitor
- Later →CVE-2022-49289Feb 26, 2025 · uaccess: fix integer overflow on access_ok()28Monitor
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 | 37b12c16beb6f6c1c3c678c1aacbc46525c250f7 | Vendor (CNA) |
| Linux Linux | 51fce708ab8986a9879ee5da946a2cc120f1036d | Vendor (CNA) |
| Linux Linux | 5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6 | Vendor (CNA) |
| Linux Linux | 69534c48ba8ce552ce383b3dfdb271ffe51820c3 | Vendor (CNA) |
| Linux Linux | a21d2f323b5a978dedf9ff1d50f101f85e39b3f2 | Vendor (CNA) |
| Linux Linux | b560d670c87d7d40b3cf6949246fa4c7aa65a00a | Vendor (CNA) |
| Linux Linux | e14dca613e0a6ddc2bf6e360f16936a9f865205b | Vendor (CNA) |
| Linux Linux | e7786c445bb67a9a6e64f66ebd6b7215b153ff7d | Vendor (CNA) |
| debian:linux | 5.17.3-1 · Debian:12 | 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/51fce708ab8986a9879ee5da946a2cc120f1036d
- git.kernel.org/stable/c/5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6
- git.kernel.org/stable/c/69534c48ba8ce552ce383b3dfdb271ffe51820c3
- git.kernel.org/stable/c/a21d2f323b5a978dedf9ff1d50f101f85e39b3f2
- git.kernel.org/stable/c/b560d670c87d7d40b3cf6949246fa4c7aa65a00a
- git.kernel.org/stable/c/e14dca613e0a6ddc2bf6e360f16936a9f865205b
- git.kernel.org/stable/c/e7786c445bb67a9a6e64f66ebd6b7215b153ff7d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.