Answer in brief
CVE-2022-49291 records a Unknown severity vulnerability in ALSA: pcm: Fix races among concurrent hw_params and hw_free calls. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-49291 records a Unknown severity vulnerability in ALSA: pcm: Fix races among concurrent hw_params and hw_free calls. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 2.6.12 | Not reported |
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a42aa926843acca96c0dfbde2e835b8137f2f092 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9cb6c40a6ebe4a0cfc9d6a181958211682cffea9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fbeb492694ce0441053de57699e1e2b7bc148a69 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0f6947f5f5208f6ebd4d76a82a4757e2839a23f8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <33061d0fba51d2bf70a2ef9645f703c33fe8e438 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0090c13cbbdffd7da079ac56f80373a9a1be0bf8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1bbf82d9f961414d6c76a08f7f843ea068e0ab7b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92ee3c60ec9fe64404dc035e7c41277d74aa26cb | a42aa926843acca96c0dfbde2e835b8137f2f092, 9cb6c40a6ebe4a0cfc9d6a181958211682cffea9, fbeb492694ce0441053de57699e1e2b7bc148a69, 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8, 33061d0fba51d2bf70a2ef9645f703c33fe8e438, 0090c13cbbdffd7da079ac56f80373a9a1be0bf8, 1bbf82d9f961414d6c76a08f7f843ea068e0ab7b, 92ee3c60ec9fe64404dc035e7c41277d74aa26cb |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent hw_params and hw_free calls Currently we have neither proper check nor protection against the concurrent calls of PCM hw_params and hw_free ioctls, which may result in a UAF. Since the existing PCM stream lock can't be used for protecting the whole ioctl operations, we need a new mutex to protect those racy calls. This patch introduced a new mutex, runtime->buffer_mutex, and applies it to both hw_params and hw_free ioctl code paths. Along with it, the both functions are slightly modified (the mmap_count check is moved into the state-check block) for code simplicity.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 2.6.12 | Not reported |
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a42aa926843acca96c0dfbde2e835b8137f2f092 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9cb6c40a6ebe4a0cfc9d6a181958211682cffea9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fbeb492694ce0441053de57699e1e2b7bc148a69 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0f6947f5f5208f6ebd4d76a82a4757e2839a23f8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <33061d0fba51d2bf70a2ef9645f703c33fe8e438 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0090c13cbbdffd7da079ac56f80373a9a1be0bf8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1bbf82d9f961414d6c76a08f7f843ea068e0ab7b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92ee3c60ec9fe64404dc035e7c41277d74aa26cb | a42aa926843acca96c0dfbde2e835b8137f2f092, 9cb6c40a6ebe4a0cfc9d6a181958211682cffea9, fbeb492694ce0441053de57699e1e2b7bc148a69, 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8, 33061d0fba51d2bf70a2ef9645f703c33fe8e438, 0090c13cbbdffd7da079ac56f80373a9a1be0bf8, 1bbf82d9f961414d6c76a08f7f843ea068e0ab7b, 92ee3c60ec9fe64404dc035e7c41277d74aa26cb |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent hw_params and hw_free calls Currently we have neither proper check nor protection against the concurrent calls of PCM hw_params and hw_free ioctls, which may result in a UAF. Since the existing PCM stream lock can't be used for protecting the whole ioctl operations, we need a new mutex to protect those racy calls. This patch introduced a new mutex, runtime->buffer_mutex, and applies it to both hw_params and hw_free ioctl code paths. Along with it, the both functions are slightly modified (the mmap_count check is moved into the state-check block) for code simplicity.
Quoted source text, attributed separately from HOL analysis.