ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock
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 w
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.110, 5.15.33, 5.16.19, 5.17.2
- CVEs
- CVE-2022-49272
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 16:14 UTC · Revision 1
Source evidence
ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock
core-osv · Original sourcePublished 26 Feb 2025, 01:56 UTC
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 w
osv:CVE-2022-49272
Kernel
Fixed versions: 5.10.110, 5.15.33, 5.16.19, 5.17.2
Complete source record
{
"id": "1bac41bd695aec0c40af5fc18f64b195b1f28ea96defbf14e6e29fe3a3cd8651",
"url": "https://osv.dev/vulnerability/CVE-2022-49272",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock",
"summary": "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 w",
"evidence": "osv:CVE-2022-49272",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.110",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.33",
"evidence": "/affected/1/ranges"
},
{
"value": "5.16.19",
"evidence": "/affected/1/ranges"
},
{
"value": "5.17.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-49272",
"aliases": [
"CVE-2022-49272"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "73867cb2bc7dfa7fbd219e53a0b68d253d8fda09"
},
{
"fixed": "7e9133607e1501c94881be35e118d8f84d96dcb4"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "b3830197aa7413c65767cf5a1aa8775c83f0dbf7"
},
{
"fixed": "40f4cffbe13a51faf136faf5f9ef6847782cd595"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "08d1807f097a63ea00a7067dad89c1c81cb2115e"
},
{
"fixed": "9661bf674d6a82b76e4ae424438a8ce1e3ed855d"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8527c8f052fb42091c6569cb928e472376a4a889"
},
{
"fixed": "9017201e8d8c6d1472273361389ed431188584a0"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "47711ff10c7e126702cfa725f6d86ef529d15a5f"
},
{
"fixed": "7777744e92a0b30e3e0cce2758d911837011ebd9"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4d1b0ace2d56dc27cc4921eda7fae57f77f03eb5"
},
{
"fixed": "abedf0d08c79d76da0d6fa0d5dbbc98871dcbc2e"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "dd2f8c684da3e226e5ec7a81c89ff5fd4a957a03"
},
{
"fixed": "be9813ad2fc8f0885f5ce6925af0d993ce5da4e5"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "dca947d4d26dbf925a64a6cfb2ddbc035e831a3d"
},
{
"fixed": "bc55cfd5718c7c23e5524582e9fa70b4d10f2433"
}
]
}
],
"versions": [
"v5.10.109",
"v5.15.32",
"v5.16.18",
"v5.17.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49272.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.10.109"
},
{
"fixed": "5.10.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.15.32"
},
{
"fixed": "5.15.33"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.18"
},
{
"fixed": "5.16.19"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.17.1"
},
{
"fixed": "5.17.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49272.json"
}
}
],
"modified": "2026-10-28T02:30:37.597511288Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/40f4cffbe13a51faf136faf5f9ef6847782cd595",
"https://git.kernel.org/stable/c/7777744e92a0b30e3e0cce2758d911837011ebd9",
"https://git.kernel.org/stable/c/7e9133607e1501c94881be35e118d8f84d96dcb4",
"https://git.kernel.org/stable/c/9017201e8d8c6d1472273361389ed431188584a0",
"https://git.kernel.org/stable/c/9661bf674d6a82b76e4ae424438a8ce1e3ed855d",
"https://git.kernel.org/stable/c/abedf0d08c79d76da0d6fa0d5dbbc98871dcbc2e",
"https://git.kernel.org/stable/c/bc55cfd5718c7c23e5524582e9fa70b4d10f2433",
"https://git.kernel.org/stable/c/be9813ad2fc8f0885f5ce6925af0d993ce5da4e5",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49272.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49272",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49272.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49272",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 504547,
"published_at": "2025-02-26T01:56:18.626+00:00"
}