Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49733: ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC

Noroxi assessment

Priority: Monitor (action score 18/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.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 4051324a6dafd7053c74c475e80b3ba10ae672b0, 723ac5ab2891b6c10dd6cc78ef5456af593490eb, 8015ef9e8a0ee5cecfd0cb6805834d007ab26f86.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.

Low priority for now. Upgrade to Linux Linux 4051324a6dafd7053c74c475e80b3ba10ae672b0, 723ac5ab2891b6c10dd6cc78ef5456af593490eb, 8015ef9e8a0ee5cecfd0cb6805834d007ab26f86 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: oss: Fix race at SNDCTL_DSP_SYNC There is a small race window at snd_pcm_oss_sync() that is called from OSS PCM SNDCTL_DSP_SYNC ioctl; namely the function calls snd_pcm_oss_make_ready() at first, then takes the params_lock mutex for the rest. When the stream is set up again by another thread between them, it leads to inconsistency, and may result in unexpected results such as NULL dereference of OSS buffer as a fuzzer spotted recently. The fix is simply to cover snd_pcm_oss_make_ready() call into the same params_lock mutex with snd_pcm_oss_make_ready_locked() variant.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Mar 2, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.7
CNA · Linux
7.8
3.1 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

Follow CVE-2022-49733

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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 5.4.215
  • linux linux kernel5.5 and later · before 5.10.148
  • linux linux kernel5.11 and later · before 5.15.68
  • linux linux kernel5.16 and later · before 5.19.9
  • linux linux kernel6.0

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.20affected
    • e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 and later · before 4051324a6dafd7053c74c475e80b3ba10ae672b0affected · git
    • e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 and later · before fce793a056c604b41a298317cf704dae255f1b36affected · git
    • e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 and later · before 8015ef9e8a0ee5cecfd0cb6805834d007ab26f86affected · git
    • e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 and later · before 723ac5ab2891b6c10dd6cc78ef5456af593490ebaffected · git
    • e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 and later · before 8423f0b6d513b259fdab9c9bf4aaa6188d054c2daffected · git
    • before 2.6.20not affected · semver
    • 5.4.215 and later · up to and including 5.4.*not affected · semver
    • 5.10.148 and later · up to and including 5.10.*not affected · semver
    • 5.15.68 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.19.11-15.19.11-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

Same product

linux: all records

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-2025-21814Feb 27, 2025 · ptp: Ensure info->enable callback is always set
    22Monitor
  • ← EarlierCVE-2025-21817Feb 27, 2025 · block: mark GFP_NOIO around sysfs ->store()
    22Monitor
  • Later →CVE-2024-51954Mar 3, 2025 · Unauthorized access to secure services in ArcGIS Server
    34Monitor

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 Linux4051324a6dafd7053c74c475e80b3ba10ae672b0Vendor (CNA)
Linux Linux723ac5ab2891b6c10dd6cc78ef5456af593490ebVendor (CNA)
Linux Linux8015ef9e8a0ee5cecfd0cb6805834d007ab26f86Vendor (CNA)
Linux Linux8423f0b6d513b259fdab9c9bf4aaa6188d054c2dVendor (CNA)
Linux Linuxfce793a056c604b41a298317cf704dae255f1b36Vendor (CNA)
debian:linux5.19.11-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.

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 researchers

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records