Acknowledged
Created: Jun 18, 2025
Updated: Sep 4, 2026
Resolved Date: Jun 19, 2025
Found In Version: 10.25.33.1
Severity: Standard
Applicable for: Wind River Linux LTS 25
Component/s: Kernel
In the Linux kernel, the following vulnerability has been resolved:EOL][EOL]binder: fix alloc->vma_vm_mm null-ptr dereference[EOL][EOL]Syzbot reported a couple issues introduced by commit 44e602b4e52f[EOL]("binder_alloc: add missing mmap_lock calls when using the VMA"), in[EOL]which we attempt to acquire the mmap_lock when alloc->vma_vm_mm has not[EOL]been initialized yet.[EOL][EOL]This can happen if a binder_proc receives a transaction without having[EOL]previously called mmap() to setup the binder_proc->alloc space in [1].[EOL]Also, a similar issue occurs via binder_alloc_print_pages() when we try[EOL]to dump the debugfs binder stats file in [2].[EOL][EOL]Sample of syzbot's crash report:[EOL] ==================================================================[EOL] KASAN: null-ptr-deref in range [0x0000000000000128-0x000000000000012f][EOL] CPU: 0 PID: 3755 Comm: syz-executor229 Not tainted 6.0.0-rc1-next-20220819-syzkaller #0[EOL] syz-executor229[3755] cmdline: ./syz-executor2294415195[EOL] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022[EOL] RIP: 0010:__lock_acquire+0xd83/0x56d0 kernel/locking/lockdep.c:4923[EOL] [...][EOL] Call Trace:[EOL] <TASK>[EOL] lock_acquire kernel/locking/lockdep.c:5666 [inline][EOL] lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631[EOL] down_read+0x98/0x450 kernel/locking/rwsem.c:1499[EOL] mmap_read_lock include/linux/mmap_lock.h:117 [inline][EOL] binder_alloc_new_buf_locked drivers/android/binder_alloc.c:405 [inline][EOL] binder_alloc_new_buf+0xa5/0x19e0 drivers/android/binder_alloc.c:593[EOL] binder_transaction+0x242e/0x9a80 drivers/android/binder.c:3199[EOL] binder_thread_write+0x664/0x3220 drivers/android/binder.c:3986[EOL] binder_ioctl_write_read drivers/android/binder.c:5036 [inline][EOL] binder_ioctl+0x3470/0x6d00 drivers/android/binder.c:5323[EOL] vfs_ioctl fs/ioctl.c:51 [inline][EOL] __do_sys_ioctl fs/ioctl.c:870 [inline][EOL] __se_sys_ioctl fs/ioctl.c:856 [inline][EOL] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856[EOL] do_syscall_x64 arch/x86/entry/common.c:50 [inline][EOL] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80[EOL] entry_SYSCALL_64_after_hwframe+0x63/0xcd[EOL] [...][EOL] ==================================================================[EOL][EOL]Fix these issues by setting up alloc->vma_vm_mm pointer during open()[EOL]and caching directly from current->mm. This guarantees we have a valid[EOL]reference to take the mmap_lock during scenarios described above.[EOL][EOL][1] https://syzkaller.appspot.com/bug?extid=f7dc54e5be28950ac459[EOL][2] https://syzkaller.appspot.com/bug?extid=a75ebe0452711c9e56d9
CREATE(Triage):(User=lchen-cn) [CVE-2022-49947 (https://nvd.nist.gov/vuln/detail/CVE-2022-49947)