Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49272: ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock

Noroxi assessment

Priority: Monitor (action score 22/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.20% (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 40f4cffbe13a51faf136faf5f9ef6847782cd595, 5.10.110, 5.15.33.

Low priority for now. Upgrade to Linux Linux 40f4cffbe13a51faf136faf5f9ef6847782cd595, 5.10.110, 5.15.33 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 potential AB/BA lock with buffer_mutex and mmap_lock syzbot caught a potential deadlock between the PCM runtime->buffer_mutex and the mm->mmap_lock. It was brought by the recent fix to cover the racy read/write and other ioctls, and in that commit, I overlooked a (hopefully only) corner case that may take the revert lock, namely, the OSS mmap. The OSS mmap operation exceptionally allows to re-configure the parameters inside the OSS mmap syscall, where mm->mmap_mutex is already held. Meanwhile, the copy_from/to_user calls at read/write operations also take the mm->mmap_lock internally, hence it may lead to a AB/BA deadlock. A similar problem was already seen in the past and we fixed it with a refcount (in commit b248371628aa). The former fix covered only the call paths with OSS read/write and OSS ioctls, while we need to cover the concurrent access via both ALSA and OSS APIs now. This patch addresses the problem above by replacing the buffer_mutex lock in the read/write operations with a refcount similar as we've used for OSS. The new field, runtime->buffer_accessing, keeps the number of concurrent read/write operations. Unlike the former buffer_mutex protection, this protects only around the copy_from/to_user() calls; the other codes are basically protected by the PCM stream lock. The refcount can be a negative, meaning blocked by the ioctls. If a negative value is seen, the read/write aborts with -EBUSY. In the ioctl side, OTOH, they check this refcount, too, and set to a negative value for blocking unless it's already being accessed.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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

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 kernel5.10.109
  • linux linux kernel5.15.32
  • linux linux kernel5.16.18
  • linux linux kernel5.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

    • 73867cb2bc7dfa7fbd219e53a0b68d253d8fda09 and later · before 7e9133607e1501c94881be35e118d8f84d96dcb4affected · git
    • b3830197aa7413c65767cf5a1aa8775c83f0dbf7 and later · before 40f4cffbe13a51faf136faf5f9ef6847782cd595affected · git
    • 08d1807f097a63ea00a7067dad89c1c81cb2115e and later · before 9661bf674d6a82b76e4ae424438a8ce1e3ed855daffected · git
    • 8527c8f052fb42091c6569cb928e472376a4a889 and later · before 9017201e8d8c6d1472273361389ed431188584a0affected · git
    • 47711ff10c7e126702cfa725f6d86ef529d15a5f and later · before 7777744e92a0b30e3e0cce2758d911837011ebd9affected · git
    • 4d1b0ace2d56dc27cc4921eda7fae57f77f03eb5 and later · before abedf0d08c79d76da0d6fa0d5dbbc98871dcbc2eaffected · git
    • dd2f8c684da3e226e5ec7a81c89ff5fd4a957a03 and later · before be9813ad2fc8f0885f5ce6925af0d993ce5da4e5affected · git
    • dca947d4d26dbf925a64a6cfb2ddbc035e831a3d and later · before bc55cfd5718c7c23e5524582e9fa70b4d10f2433affected · git
    • 5.10.109 and later · before 5.10.110affected · semver
    • 5.15.32 and later · before 5.15.33affected · 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

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-49270Feb 26, 2025 · dm: fix use-after-free in dm_cleanup_zoned_dev()
    31Monitor
  • ← EarlierCVE-2022-49271Feb 26, 2025 · cifs: prevent bad output lengths in smb2_ioctl_query_info()
    22Monitor
  • Later →CVE-2022-49273Feb 26, 2025 · rtc: pl031: fix rtc features null pointer dereference
    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 Linux40f4cffbe13a51faf136faf5f9ef6847782cd595Vendor (CNA)
Linux Linux5.10.110Vendor (CNA)
Linux Linux5.15.33Vendor (CNA)
Linux Linux5.16.19Vendor (CNA)
Linux Linux5.17.2Vendor (CNA)
Linux Linux7777744e92a0b30e3e0cce2758d911837011ebd9Vendor (CNA)
Linux Linux7e9133607e1501c94881be35e118d8f84d96dcb4Vendor (CNA)
Linux Linux9017201e8d8c6d1472273361389ed431188584a0Vendor (CNA)
Linux Linux9661bf674d6a82b76e4ae424438a8ce1e3ed855dVendor (CNA)
Linux Linuxabedf0d08c79d76da0d6fa0d5dbbc98871dcbc2eVendor (CNA)
Linux Linuxbc55cfd5718c7c23e5524582e9fa70b4d10f2433Vendor (CNA)
Linux Linuxbe9813ad2fc8f0885f5ce6925af0d993ce5da4e5Vendor (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.

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records