| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM |
| |
| We currently assume that there is at least one VMA in a MM, which isn't |
| true. |
| |
| So we might end up having find_vma() return NULL, to then de-reference |
| NULL. So properly handle find_vma() returning NULL. |
| |
| This fixes the report: |
| |
| Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI |
| KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] |
| CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0 |
| Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 |
| RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline] |
| RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194 |
| Code: ... |
| RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246 |
| RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000 |
| RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044 |
| RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1 |
| R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003 |
| R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8 |
| FS: 00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 |
| CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 |
| CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0 |
| DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 |
| DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 |
| Call Trace: |
| <TASK> |
| kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 |
| __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] |
| __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] |
| __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 |
| do_syscall_x64 arch/x86/entry/common.c:52 [inline] |
| do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 |
| entry_SYSCALL_64_after_hwframe+0x77/0x7f |
| |
| [akpm@linux-foundation.org: add unlikely()] |
| |
| The Linux kernel CVE team has assigned CVE-2024-56611 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.16 with commit 39743889aaf76725152f16aa90ca3c45f6d52da3 and fixed in 6.6.66 with commit a13b2b9b0b0b04612c7d81e3b3dfb485c5f7abc3 |
| Issue introduced in 2.6.16 with commit 39743889aaf76725152f16aa90ca3c45f6d52da3 and fixed in 6.12.5 with commit 42d9fe2adf8613f9eea1f0c2619c9e2611eae0ea |
| Issue introduced in 2.6.16 with commit 39743889aaf76725152f16aa90ca3c45f6d52da3 and fixed in 6.13 with commit 091c1dd2d4df6edd1beebe0e5863d4034ade9572 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-56611 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| mm/mempolicy.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/a13b2b9b0b0b04612c7d81e3b3dfb485c5f7abc3 |
| https://git.kernel.org/stable/c/42d9fe2adf8613f9eea1f0c2619c9e2611eae0ea |
| https://git.kernel.org/stable/c/091c1dd2d4df6edd1beebe0e5863d4034ade9572 |
