{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.2-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.2-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.2-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  binder: fix alloc-\u003evma_vm_mm null-ptr dereference  Syzbot reported a couple issues introduced by commit 44e602b4e52f (\"binder_alloc: add missing mmap_lock calls when using the VMA\"), in which we attempt to acquire the mmap_lock when alloc-\u003evma_vm_mm has not been initialized yet.  This can happen if a binder_proc receives a transaction without having previously called mmap() to setup the binder_proc-\u003ealloc space in [1]. Also, a similar issue occurs via binder_alloc_print_pages() when we try to dump the debugfs binder stats file in [2].  Sample of syzbot's crash report:   ==================================================================   KASAN: null-ptr-deref in range [0x0000000000000128-0x000000000000012f]   CPU: 0 PID: 3755 Comm: syz-executor229 Not tainted 6.0.0-rc1-next-20220819-syzkaller #0   syz-executor229[3755] cmdline: ./syz-executor2294415195   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022   RIP: 0010:__lock_acquire+0xd83/0x56d0 kernel/locking/lockdep.c:4923   [...]   Call Trace:    \u003cTASK\u003e    lock_acquire kernel/locking/lockdep.c:5666 [inline]    lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631    down_read+0x98/0x450 kernel/locking/rwsem.c:1499    mmap_read_lock include/linux/mmap_lock.h:117 [inline]    binder_alloc_new_buf_locked drivers/android/binder_alloc.c:405 [inline]    binder_alloc_new_buf+0xa5/0x19e0 drivers/android/binder_alloc.c:593    binder_transaction+0x242e/0x9a80 drivers/android/binder.c:3199    binder_thread_write+0x664/0x3220 drivers/android/binder.c:3986    binder_ioctl_write_read drivers/android/binder.c:5036 [inline]    binder_ioctl+0x3470/0x6d00 drivers/android/binder.c:5323    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:870 [inline]    __se_sys_ioctl fs/ioctl.c:856 [inline]    __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856    do_syscall_x64 arch/x86/entry/common.c:50 [inline]    do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80    entry_SYSCALL_64_after_hwframe+0x63/0xcd    [...]   ==================================================================  Fix these issues by setting up alloc-\u003evma_vm_mm pointer during open() and caching directly from current-\u003emm. This guarantees we have a valid reference to take the mmap_lock during scenarios described above.  [1] https://syzkaller.appspot.com/bug?extid=f7dc54e5be28950ac459 [2] https://syzkaller.appspot.com/bug?extid=a75ebe0452711c9e56d9",
  "id": "DEBIAN-CVE-2022-49947",
  "modified": "2026-09-01T19:48:27.985144523Z",
  "published": "2025-06-18T11:15:21.717Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2022-49947"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2022-49947"
  ]
}