Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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).

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

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.

Follow CVE-2022-49288

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.17.3-15.17.3-1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-defaultbefore 3.0.101-108.180.13.0.101-108.180.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-docsbefore 3.0.101-108.180.13.0.101-108.180.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-ec2before 3.0.101-108.180.13.0.101-108.180.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-sourcebefore 3.0.101-108.180.13.0.101-108.180.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-symsbefore 3.0.101-108.180.13.0.101-108.180.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-tracebefore 3.0.101-108.180.13.0.101-108.180.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-xenbefore 3.0.101-108.180.13.0.101-108.180.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49286Feb 26, 2025 · tpm: use try_get_ops() in tpm-space.c
    18Monitor
  • ← EarlierCVE-2022-49287Feb 26, 2025 · tpm: fix reference counting for struct tpm_chip
    28Monitor
  • 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 / packageFixed versionSource
Linux Linux37b12c16beb6f6c1c3c678c1aacbc46525c250f7Vendor (CNA)
Linux Linux51fce708ab8986a9879ee5da946a2cc120f1036dVendor (CNA)
Linux Linux5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6Vendor (CNA)
Linux Linux69534c48ba8ce552ce383b3dfdb271ffe51820c3Vendor (CNA)
Linux Linuxa21d2f323b5a978dedf9ff1d50f101f85e39b3f2Vendor (CNA)
Linux Linuxb560d670c87d7d40b3cf6949246fa4c7aa65a00aVendor (CNA)
Linux Linuxe14dca613e0a6ddc2bf6e360f16936a9f865205bVendor (CNA)
Linux Linuxe7786c445bb67a9a6e64f66ebd6b7215b153ff7dVendor (CNA)
debian:linux5.17.3-1 · Debian:12Package registry (OSV)
suse:kernel-default3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-docs3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-ec23.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-source3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-syms3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-trace3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-xen3.0.101-108.180.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage 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.

EPSS, last 120 days

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.

Finders, 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 Free

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records