CVE-2021-47281
published 2024-05-21CVE-2021-47281: In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix race of snd_seq_timer_open() The timer instance per queue is exclusive, and…
PriorityP428high7CVSS 3.1
AVLACHPRLUINSUCHIHAH
EPSS
0.23%
14.5th percentile
In the Linux kernel, the following vulnerability has been resolved:
ALSA: seq: Fix race of snd_seq_timer_open()
The timer instance per queue is exclusive, and snd_seq_timer_open()
should have managed the concurrent accesses. It looks as if it's
checking the already existing timer instance at the beginning, but
it's not right, because there is no protection, hence any later
concurrent call of snd_seq_timer_open() may override the timer
instance easily. This may result in UAF, as the leftover timer
instance can keep running while the queue itself gets closed, as
spotted by syzkaller recently.
For avoiding the race, add a proper check at the assignment of
tmr->timeri again, and return -EBUSY if it's been already registered.
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.46-1 (bookworm) | linux 5.10.46-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bd7d88b0874f82f7b29d1a53e574cedaf23166ba | bd7d88b0874f82f7b29d1a53e574cedaf23166ba |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 536a7646c00a0f14fee49e5e313109e5da2f6031 | 536a7646c00a0f14fee49e5e313109e5da2f6031 |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 83e197a8414c0ba545e7e3916ce05f836f349273 | 83e197a8414c0ba545e7e3916ce05f836f349273 |
| linux | linux_kernel | < 5.10.44 | 5.10.44 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 5.11 < 5.12.11 | 5.12.11 |
CVSS provenance
nvdv3.17.0HIGHCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.0HIGH
vendor_debian7.0HIGH
vendor_redhat7.0HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-fj34-p4r2-ghh5: In the Linux kernel, the following vulnerability has been resolved:
ALSA: seq: Fix race of snd_seq_timer_open()
The timer instance per queue is excl
ghsa_unreviewed·2024-05-21
CVE-2021-47281 [HIGH] CWE-416 GHSA-fj34-p4r2-ghh5: In the Linux kernel, the following vulnerability has been resolved:
ALSA: seq: Fix race of snd_seq_timer_open()
The timer instance per queue is excl
In the Linux kernel, the following vulnerability has been resolved:
ALSA: seq: Fix race of snd_seq_timer_open()
The timer instance per queue is exclusive, and snd_seq_timer_open()
should have managed the concurrent accesses. It looks as if it's
checking the already existing timer instance at the beginning, but
it's not right, because there is no protection, hence any later
concurrent call of snd_seq_timer_open() may override the timer
instance easily. This may result in UAF, as the leftover timer
instance can keep running while the queue itself gets closed, as
spotted by syzkaller recently.
For avoiding the race, add a proper check at the assignment of
tmr->timeri again, and return -EBUSY if it's been already registered.
OSV
CVE-2021-47281: In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix race of snd_seq_timer_open() The timer instance per queue is exclus
osv·2024-05-21·CVSS 7.0
CVE-2021-47281 [HIGH] CVE-2021-47281: In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix race of snd_seq_timer_open() The timer instance per queue is exclus
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix race of snd_seq_timer_open() The timer instance per queue is exclusive, and snd_seq_timer_open() should have managed the concurrent accesses. It looks as if it's checking the already existing timer instance at the beginning, but it's not right, because there is no protection, hence any later concurrent call of snd_seq_timer_open() may override the timer instance easily. This may result in UAF, as the leftover timer instance can keep running while the queue itself gets closed, as spotted by syzkaller recently. For avoiding the race, add a proper check at the assignment of tmr->timeri again, and return -EBUSY if it's been already registered.
Red Hat
kernel: ALSA: seq: Fix race of snd_seq_timer_open()
vendor_redhat·2024-05-21·CVSS 7.0
CVE-2021-47281 [HIGH] CWE-416 kernel: ALSA: seq: Fix race of snd_seq_timer_open()
kernel: ALSA: seq: Fix race of snd_seq_timer_open()
In the Linux kernel, the following vulnerability has been resolved:
ALSA: seq: Fix race of snd_seq_timer_open()
The timer instance per queue is exclusive, and snd_seq_timer_open()
should have managed the concurrent accesses. It looks as if it's
checking the already existing timer instance at the beginning, but
it's not right, because there is no protection, hence any later
concurrent call of snd_seq_timer_open() may override the timer
instance easily. This may result in UAF, as the leftover timer
instance can keep running while the queue itself gets closed, as
spotted by syzkaller recently.
For avoiding the race, add a proper check at the assignment of
tmr->timeri again, and return -EBUSY if it's been already registered.
A vulnerability
Debian
CVE-2021-47281: linux - In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: ...
vendor_debian·2021·CVSS 7.0
CVE-2021-47281 [HIGH] CVE-2021-47281: linux - In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: ...
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix race of snd_seq_timer_open() The timer instance per queue is exclusive, and snd_seq_timer_open() should have managed the concurrent accesses. It looks as if it's checking the already existing timer instance at the beginning, but it's not right, because there is no protection, hence any later concurrent call of snd_seq_timer_open() may override the timer instance easily. This may result in UAF, as the leftover timer instance can keep running while the queue itself gets closed, as spotted by syzkaller recently. For avoiding the race, add a proper check at the assignment of tmr->timeri again, and return -EBUSY if it's been already registered.
Scope: local
bookworm: resolved (fixed in 5.10.46-1)
bullseye: resolv
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/536a7646c00a0f14fee49e5e313109e5da2f6031https://git.kernel.org/stable/c/83e197a8414c0ba545e7e3916ce05f836f349273https://git.kernel.org/stable/c/bd7d88b0874f82f7b29d1a53e574cedaf23166bahttps://git.kernel.org/stable/c/536a7646c00a0f14fee49e5e313109e5da2f6031https://git.kernel.org/stable/c/83e197a8414c0ba545e7e3916ce05f836f349273https://git.kernel.org/stable/c/bd7d88b0874f82f7b29d1a53e574cedaf23166ba
2024-05-21
Published