CVE-2023-52438 json
binder: fix use-after-free in shinker's callback
published 2y ago modified 3mo ago also EUVD-2023-57063
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.4.268, 5.10.209, 5.15.148, 6.1.74, 6.6.13, 6.7.1, 6.8
- linux Debian 12 6.1.76-1
- linux Debian 14, Debian 13 6.6.13-1
debian advisories DEBIAN-CVE-2023-52438
- linux Ubuntu 20.04 LTS 5.4.0-176.196
- linux Ubuntu 22.04 LTS 5.15.0-102.112
- linux-aws Ubuntu 20.04 LTS 5.4.0-1122.132
- linux-aws Ubuntu 22.04 LTS 5.15.0-1057.63
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1126.135
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1055.63
- linux-gke Ubuntu 22.04 LTS 5.15.0-1054.59
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1069.74
ubuntu advisories UBUNTU-CVE-2023-52438
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/a53e15e592b4dcc91c3a3b8514e484a0bdbc53a3 commit
- git.kernel.org/stable/c/c8c1158ffb007197f31f9d9170cf13e4f34cbb5c commit
- git.kernel.org/stable/c/8ad4d580e8aff8de2a4d57c5930fcc29f1ffd4a6 commit
- git.kernel.org/stable/c/9fa04c93f24138747807fe75b5591bb680098f56 commit
- git.kernel.org/stable/c/a49087ab93508b60d9b8add91707a22dda832869 commit
- git.kernel.org/stable/c/e074686e993ff1be5f21b085a3b1b4275ccd5727 commit
- git.kernel.org/stable/c/3f489c2067c5824528212b0fc18b28d51332d906 commit
Is CVE-2023-52438 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-52438 updated cvss 7.8
kernel: binder: fix use-after-free in shinker's callback
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +82 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-20).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/a53e15e592b4dcc91c3a3b8514e484a0bdbc53a3
patch
-
git.kernel.org
/stable/c/c8c1158ffb007197f31f9d9170cf13e4f34cbb5c
patch
-
git.kernel.org
/stable/c/8ad4d580e8aff8de2a4d57c5930fcc29f1ffd4a6
patch
-
git.kernel.org
/stable/c/9fa04c93f24138747807fe75b5591bb680098f56
patch
-
git.kernel.org
/stable/c/a49087ab93508b60d9b8add91707a22dda832869
patch
-
git.kernel.org
/stable/c/e074686e993ff1be5f21b085a3b1b4275ccd5727
patch
-
git.kernel.org
/stable/c/3f489c2067c5824528212b0fc18b28d51332d906
patch
- lists.debian.org /debian-lts-announce/2024/06/msg00016.html
Sources
- CVE List CVE-2023-52438
- NVD CVE-2023-52438
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.