CVE-2026-43416

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> powerpc, perf: Check that current-&gt;mm is alive before getting user callchain<br /> <br /> It may happen that mm is already released, which leads to kernel panic.<br /> This adds the NULL check for current-&gt;mm, similarly to<br /> commit 20afc60f892d ("x86, perf: Check that current-&gt;mm is alive before getting user callchain").<br /> <br /> I was getting this panic when running a profiling BPF program<br /> (profile.py from bcc-tools):<br /> <br /> [26215.051935] Kernel attempted to read user page (588) - exploit attempt? (uid: 0)<br /> [26215.051950] BUG: Kernel NULL pointer dereference on read at 0x00000588<br /> [26215.051952] Faulting instruction address: 0xc00000000020fac0<br /> [26215.051957] Oops: Kernel access of bad area, sig: 11 [#1]<br /> [...]<br /> [26215.052049] Call Trace:<br /> [26215.052050] [c000000061da6d30] [c00000000020fc10] perf_callchain_user_64+0x2d0/0x490 (unreliable)<br /> [26215.052054] [c000000061da6dc0] [c00000000020f92c] perf_callchain_user+0x1c/0x30<br /> [26215.052057] [c000000061da6de0] [c0000000005ab2a0] get_perf_callchain+0x100/0x360<br /> [26215.052063] [c000000061da6e70] [c000000000573bc8] bpf_get_stackid+0x88/0xf0<br /> [26215.052067] [c000000061da6ea0] [c008000000042258] bpf_prog_16d4ab9ab662f669_do_perf_event+0xf8/0x274<br /> [...]<br /> <br /> In addition, move storing the top-level stack entry to generic<br /> perf_callchain_user to make sure the top-evel entry is always captured,<br /> even if current-&gt;mm is NULL.<br /> <br /> [Maddy: fixed message to avoid checkpatch format style error]