UBUNTU-CVE-2023-52438
In the Linux kernel, the following vulnerability has been resolved: binder: fix use-after-free in shinker's callback The mmap read lock is used during the shrinker's callback, which means that using alloc->vma pointer isn't safe as it can race with munmap(). As of commit dd2283f2605e ("mm: mmap: zap pages with read mmap_sem in munmap") the mmap lock is downgraded after the vma has been isolated. I was able to reproduce this issue by manually adding some delays and triggering page reclaiming through the shrinker's debug sysfs. The following KASAN report confirms the UAF: ================================================================== BUG: KASAN: slab-use-after-free in zap_page_range_single+0x470/0x4b8 Read of size 8 at addr ffff356ed50e50f0 by task bash/478 CPU: 1 PID: 478 Comm: bash Not tainted 6.6.0-rc5-00055-g1c8b86a3799f-dirty #70 Hardware name: linux,dummy-virt (DT) Call trace: zap_page_range_single+0x470/0x4b8 binder_alloc_free_page+0x608/0xadc __list_lru_walk_one+0x130/0x3b0 list_lru_walk_node+0xc4/0x22c binder_shrink_scan+0x108/0x1dc shrinker_debugfs_scan_write+0x2b4/0x500 full_proxy_write+0xd4/0x140 vfs_write+0x1ac/0x758 ksys_write+0xf0/0x1dc __arm64_sys_write+0x6c/0x9c Allocated by task 492: kmem_cache_alloc+0x130/0x368 vm_area_alloc+0x2c/0x190 mmap_region+0x258/0x18bc do_mmap+0x694/0xa60 vm_mmap_pgoff+0x170/0x29c ksys_mmap_pgoff+0x290/0x3a0 __arm64_sys_mmap+0xcc/0x144 Freed by task 491: kmem_cache_free+0x17c/0x3c8 vm_area_free_rcu_cb+0x74/0x98 rcu_core+0xa38/0x26d4 rcu_core_si+0x10/0x1c __do_softirq+0x2fc/0xd24 Last potentially related work creation: __call_rcu_common.constprop.0+0x6c/0xba0 call_rcu+0x10/0x1c vm_area_free+0x18/0x24 remove_vma+0xe4/0x118 do_vmi_align_munmap.isra.0+0x718/0xb5c do_vmi_munmap+0xdc/0x1fc __vm_munmap+0x10c/0x278 __arm64_sys_munmap+0x58/0x7c Fix this issue by performing instead a vma_lookup() which will fail to find the vma that was isolated before the mmap lock downgrade. Note that this option has better performance than upgrading to a mmap write lock which would increase contention. Plus, mmap_write_trylock() has been recently removed anyway.
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
27 explicit affected versions
39 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
6 explicit affected versions
48 explicit affected versions
34 explicit affected versions
55 explicit affected versions
45 explicit affected versions
34 explicit affected versions
10 explicit affected versions
41 explicit affected versions
7 explicit affected versions
42 explicit affected versions
82 explicit affected versions
13 explicit affected versions
35 explicit affected versions
1 explicit affected versions
13 explicit affected versions
18 explicit affected versions
3 explicit affected versions
28 explicit affected versions
84 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
21 explicit affected versions
9 explicit affected versions
16 explicit affected versions
10 explicit affected versions
39 explicit affected versions
7 explicit affected versions
12 explicit affected versions
32 explicit affected versions
12 explicit affected versions
14 explicit affected versions
7 explicit affected versions
72 explicit affected versions
12 explicit affected versions
87 explicit affected versions
95 explicit affected versions
12 explicit affected versions
83 explicit affected versions
8 explicit affected versions
10 explicit affected versions
37 explicit affected versions
13 explicit affected versions
10 explicit affected versions
21 explicit affected versions
1 explicit affected versions
25 explicit affected versions
26 explicit affected versions
13 explicit affected versions
4 explicit affected versions
29 explicit affected versions
76 explicit affected versions
13 explicit affected versions
45 explicit affected versions
71 explicit affected versions
43 explicit affected versions
87 explicit affected versions
5 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
11 explicit affected versions
12 explicit affected versions
7 explicit affected versions
12 explicit affected versions
86 explicit affected versions
34 explicit affected versions
26 explicit affected versions
42 explicit affected versions
10 explicit affected versions
26 explicit affected versions
21 explicit affected versions
1 explicit affected versions
13 explicit affected versions
45 explicit affected versions
16 explicit affected versions
45 explicit affected versions
35 explicit affected versions
3 explicit affected versions
1 explicit affected versions
2 explicit affected versions
52 explicit affected versions
51 explicit affected versions
1 explicit affected versions
12 explicit affected versions
32 explicit affected versions
25 explicit affected versions
18 explicit affected versions
1 explicit affected versions
8 explicit affected versions
6 explicit affected versions
5 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
13 explicit affected versions
75 explicit affected versions
13 explicit affected versions
39 explicit affected versions
7 explicit affected versions
37 explicit affected versions
10 explicit affected versions
11 explicit affected versions
12 explicit affected versions
74 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
31 explicit affected versions
37 explicit affected versions
14 explicit affected versions
38 explicit affected versions
35 explicit affected versions
9 explicit affected versions
34 explicit affected versions
11 explicit affected versions
42 explicit affected versions
8 explicit affected versions
7 explicit affected versions
16 explicit affected versions
46 explicit affected versions
4 explicit affected versions
1 explicit affected versions
1 explicit affected versions
40 explicit affected versions
13 explicit affected versions
43 explicit affected versions
40 explicit affected versions
10 explicit affected versions
8 explicit affected versions
14 explicit affected versions
75 explicit affected versions
4 explicit affected versions
64 explicit affected versions
3 explicit affected versions
1 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: binder: fix use-after-free in shinker's callback The mmap read lock is used during the shrinker's callback, which means that using alloc->vma pointer isn't safe as it can race with munmap(). As of commit dd2283f2605e ("mm: mmap: zap pages with read mmap_sem in munmap") the mmap lock is downgraded after the vma has been isolated. I was able to reproduce this issue by manually adding some delays and triggering page reclaiming through the shrinker's debug sysfs. The following KASAN report confirms the UAF: ================================================================== BUG: KASAN: slab-use-after-free in zap_page_range_single+0x470/0x4b8 Read of size 8 at addr ffff356ed50e50f0 by task bash/478 CPU: 1 PID: 478 Comm: bash Not tainted 6.6.0-rc5-00055-g1c8b86a3799f-dirty #70 Hardware name: linux,dummy-virt (DT) Call trace: zap_page_range_single+0x470/0x4b8 binder_alloc_free_page+0x608/0xadc __list_lru_walk_one+0x130/0x3b0 list_lru_walk_node+0xc4/0x22c binder_shrink_scan+0x108/0x1dc shrinker_debugfs_scan_write+0x2b4/0x500 full_proxy_write+0xd4/0x140 vfs_write+0x1ac/0x758 ksys_write+0xf0/0x1dc __arm64_sys_write+0x6c/0x9c Allocated by task 492: kmem_cache_alloc+0x130/0x368 vm_area_alloc+0x2c/0x190 mmap_region+0x258/0x18bc do_mmap+0x694/0xa60 vm_mmap_pgoff+0x170/0x29c ksys_mmap_pgoff+0x290/0x3a0 __arm64_sys_mmap+0xcc/0x144 Freed by task 491: kmem_cache_free+0x17c/0x3c8 vm_area_free_rcu_cb+0x74/0x98 rcu_core+0xa38/0x26d4 rcu_core_si+0x10/0x1c __do_softirq+0x2fc/0xd24 Last potentially related work creation: __call_rcu_common.constprop.0+0x6c/0xba0 call_rcu+0x10/0x1c vm_area_free+0x18/0x24 remove_vma+0xe4/0x118 do_vmi_align_munmap.isra.0+0x718/0xb5c do_vmi_munmap+0xdc/0x1fc __vm_munmap+0x10c/0x278 __arm64_sys_munmap+0x58/0x7c Fix this issue by performing instead a vma_lookup() which will fail to find the vma that was isolated before the mmap lock downgrade. Note that this option has better performance than upgrading to a mmap write lock which would increase contention. Plus, mmap_write_trylock() has been recently removed anyway.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/3f489c2067c5824528212b0fc18b28d51332d906
- https://git.kernel.org/stable/c/3f489c2067c5824528212b0fc18b28d51332d906
- https://git.kernel.org/stable/c/8ad4d580e8aff8de2a4d57c5930fcc29f1ffd4a6
- https://git.kernel.org/stable/c/9fa04c93f24138747807fe75b5591bb680098f56
- https://git.kernel.org/stable/c/a49087ab93508b60d9b8add91707a22dda832869
- https://git.kernel.org/stable/c/a53e15e592b4dcc91c3a3b8514e484a0bdbc53a3
- https://git.kernel.org/stable/c/c8c1158ffb007197f31f9d9170cf13e4f34cbb5c
- https://git.kernel.org/stable/c/e074686e993ff1be5f21b085a3b1b4275ccd5727
- https://ubuntu.com/security/CVE-2023-52438
- https://ubuntu.com/security/notices/USN-6688-1
- https://ubuntu.com/security/notices/USN-6724-1
- https://ubuntu.com/security/notices/USN-6724-2
- https://ubuntu.com/security/notices/USN-6725-1
- https://ubuntu.com/security/notices/USN-6725-2
- https://ubuntu.com/security/notices/USN-6726-1
- https://ubuntu.com/security/notices/USN-6726-2
- https://ubuntu.com/security/notices/USN-6726-3
- https://www.cve.org/CVERecord?id=CVE-2023-52438