ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fd137bf8149bc6460f9b7b1fc292025da04cb9ee, Kernel 4.15, Kernel 4.20 and 16 more.
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF snd_pcm_hw_params() and snd_pcm_hw_free() guard buffer reallocation with an mmap_count check performed under the PCM stream lock, but the lock is released long before the buffer is actually freed: snd_pcm_sync_stop(), constraint refinement and do_free_pages() all happen in between. snd_pcm_mmap_data(), on the other hand, takes no lock at all: it validates against the old buffer's state and dma_bytes, remaps its pages into the VMA, and only then increments mmap_count. A concurrent mmap() can therefore slip in between the check and the free. remap_pfn_range() installs writable PTEs for the old buffer's pages without taking page references, and the subsequent do_free_pages() returns those pages to the page allocator while the VMA still maps them. This leaves a stale, writable mapping of freed pages: a page-level use-after-free that can be leveraged for local privilege escalation. Make snd_pcm_mmap_data() participate in the buffer-access scheme introduced for hw_params/hw_free: acquire runtime->buffer_accessing before validating and remapping, and release it afterwards. Buffer reallocation already fails with -EBUSY while accessors are active, and the mmap side now fails with -EBUSY while a reallocation is in progress, so the validate/remap sequence and the check/free sequence can no longer interleave. A reproducer that turns this race into a stale writable mapping of the freed DMA buffer pages is available on request.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=92ee3c60ec9fe64404dc035e7c41277d74aa26cb <fd137bf8149bc6460f9b7b1fc292025da04cb9ee, >=4.14.279 <4.15, >=4.19.243 <4.20, >=5.10.109 <5.11, >=5.15.32 <5.15.222, >=5.16.18 <5.17, >=5.17.1 <5.18, >=5.4.193 <5.5, >=92ee3c60ec9fe64404dc035e7c41277d74aa26cb <8c1882dfee8f404d118020664b73eb4592172226, >=92ee3c60ec9fe64404dc035e7c41277d74aa26cb <9857a75714bb5df4781e4d8b1a1753b1e17bf07a, >=92ee3c60ec9fe64404dc035e7c41277d74aa26cb <9b110a9dcecc59516c77cb3c0caf1f492f75df2d, >=92ee3c60ec9fe64404dc035e7c41277d74aa26cb <cbadf2575d25e7dcc0d4da2717817ae569fbc99b, >=92ee3c60ec9fe64404dc035e7c41277d74aa26cb <cbc7ec97601d09b74e05e44470fa6b0bcdabf3f5, =0090c13cbbdffd7da079ac56f80373a9a1be0bf8, =0f6947f5f5208f6ebd4d76a82a4757e2839a23f8, =1bbf82d9f961414d6c76a08f7f843ea068e0ab7b, =5.18, =9cb6c40a6ebe4a0cfc9d6a181958211682cffea9, =a42aa926843acca96c0dfbde2e835b8137f2f092, =fbeb492694ce0441053de57699e1e2b7bc148a69, >=33061d0fba51d2bf70a2ef9645f703c33fe8e438 <e6cdd2a0470d64073349a970dc1691433804b271 | fd137bf8149bc6460f9b7b1fc292025da04cb9ee, 4.15, 4.20, 5.11, 5.15.222, 5.17, 5.18, 5.5, 8c1882dfee8f404d118020664b73eb4592172226, 9857a75714bb5df4781e4d8b1a1753b1e17bf07a, 9b110a9dcecc59516c77cb3c0caf1f492f75df2d, cbadf2575d25e7dcc0d4da2717817ae569fbc99b, cbc7ec97601d09b74e05e44470fa6b0bcdabf3f5, e6cdd2a0470d64073349a970dc1691433804b271 |
| linux-kernel: Kernel | >=4.19.243 <4.20, >=5.10.109 <5.11, >=5.15.32 <5.15.222, >=5.16.18 <5.17, >=5.17.1 <5.18, >=5.18.0 <6.1.189, >=5.4.193 <5.5, >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.2.0 <6.6.158, >=6.7.0 <6.12.111, >=4.14.279 <4.15 | 4.20, 5.11, 5.15.222, 5.17, 5.18, 6.1.189, 5.5, 6.18.53, 7.2.7, 6.6.158, 6.12.111, 4.15 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket