Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49292: ALSA: oss: Fix PCM OSS buffer allocation overflow

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 0c4190b41a69990666b4000999e27f8f1b2a426b, 5ce74ff7059341d8b2f4d01c3383491df63d1898, 7a40cbf3579a8e14849ba7ce46309c1992658d2b.

Low priority for now. Upgrade to Linux Linux 0c4190b41a69990666b4000999e27f8f1b2a426b, 5ce74ff7059341d8b2f4d01c3383491df63d1898, 7a40cbf3579a8e14849ba7ce46309c1992658d2b 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: oss: Fix PCM OSS buffer allocation overflow We've got syzbot reports hitting INT_MAX overflow at vmalloc() allocation that is called from snd_pcm_plug_alloc(). Although we apply the restrictions to input parameters, it's based only on the hw_params of the underlying PCM device. Since the PCM OSS layer allocates a temporary buffer for the data conversion, the size may become unexpectedly large when more channels or higher rates is given; in the reported case, it went over INT_MAX, hence it hits WARN_ON(). This patch is an attempt to avoid such an overflow and an allocation for too large buffers. First off, it adds the limit of 1MB as the upper bound for period bytes. This must be large enough for all use cases, and we really don't want to handle a larger temporary buffer than this size. The size check is performed at two places, where the original period bytes is calculated and where the plugin buffer size is calculated. In addition, the driver uses array_size() and array3_size() for multiplications to catch overflows for the converted period size and buffer bytes.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 21th 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%

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

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-49292

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 4.19.237
  • linux linux kernel4.20 and later · before 5.4.188
  • 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

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 a63af1baf0a5e11827db60e3127f87e437cab6e5affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0c4190b41a69990666b4000999e27f8f1b2a426baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5ce74ff7059341d8b2f4d01c3383491df63d1898affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7a40cbf3579a8e14849ba7ce46309c1992658d2baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fb08bf99195a87c798bc8ae1357337a981faeadeaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e74a069c6a7bb505f3ade141dddf85f4b0b5145aaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before efb6402c3c4a7c26d97c92d70186424097b6e366affected · git
    • before 2.6.12not affected · semver
    • 4.19.237 and later · up to and including 4.19.*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.17.3-15.17.3-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-2022-49290Feb 26, 2025 · mac80211: fix potential double free on mesh join
    31Monitor
  • ← EarlierCVE-2022-49291Feb 26, 2025 · ALSA: pcm: Fix races among concurrent hw_params and hw_free calls
    31Monitor
  • Later →CVE-2022-49293Feb 26, 2025 · netfilter: nf_tables: initialize registers in nft_do_chain()
    22Monitor

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 Linux0c4190b41a69990666b4000999e27f8f1b2a426bVendor (CNA)
Linux Linux5ce74ff7059341d8b2f4d01c3383491df63d1898Vendor (CNA)
Linux Linux7a40cbf3579a8e14849ba7ce46309c1992658d2bVendor (CNA)
Linux Linuxa63af1baf0a5e11827db60e3127f87e437cab6e5Vendor (CNA)
Linux Linuxe74a069c6a7bb505f3ade141dddf85f4b0b5145aVendor (CNA)
Linux Linuxefb6402c3c4a7c26d97c92d70186424097b6e366Vendor (CNA)
Linux Linuxfb08bf99195a87c798bc8ae1357337a981faeadeVendor (CNA)
debian:linux5.17.3-1 · Debian:12Package 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.
  • 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-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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

  1. Fix✗ → ✓

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

References

Show all references (6 more)

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

All records