https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 03:51:55 +0000 https://vulnerability.circl.lu/vuln/cve-2024-56613 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sched/numa: fix memory leak due to the overwritten vma-&gt;numab_state</p> <p>[Problem Description] When running the hackbench program of LTP, the following memory leak is reported by kmemleak.</p> <p># /opt/ltp/testcases/bin/hackbench 20 thread 1000 Running with 20*40 (== 800) tasks.</p> <p># dmesg | grep kmemleak ... kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)</p> <p># cat /sys/kernel/debug/kmemleak unreferenced object 0xffff888cd8ca2c40 (size 64): comm &#34;hackbench&#34;, pid 17142, jiffies 4299780315 hex dump (first 32 bytes): ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00 .tI.....L.I..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc bff18fd4): [&lt;ffffffff81419a89&gt;] __kmalloc_cache_noprof+0x2f9/0x3f0 [&lt;ffffffff8113f715&gt;] task_numa_work+0x725/0xa00 [&lt;ffffffff8110f878&gt;] task_work_run+0x58/0x90 [&lt;ffffffff81ddd9f8&gt;] syscall_exit_to_user_mode+0x1c8/0x1e0 [&lt;ffffffff81dd78d5&gt;] do_syscall_64+0x85/0x150 [&lt;ffffffff81e0012b&gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e ...</p> <p>This issue can be consistently reproduced on three different servers: * a 448-core server * a 256-core server * a 192-core server</p> <p>[Root Cause] Since multiple threads are created by the hackbench program (along with the command argument &#39;thread&#39;), a shared vma…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sched/numa: fix memory leak due to the overwritten vma-&gt;numab_state</p> <p>[Problem Description] When running the hackbench program of LTP, the following memory leak is reported by kmemleak.</p> <p># /opt/ltp/testcases/bin/hackbench 20 thread 1000 Running with 20*40 (== 800) tasks.</p> <p># dmesg | grep kmemleak ... kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)</p> <p># cat /sys/kernel/debug/kmemleak unreferenced object 0xffff888cd8ca2c40 (size 64): comm &#34;hackbench&#34;, pid 17142, jiffies 4299780315 hex dump (first 32 bytes): ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00 .tI.....L.I..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc bff18fd4): [&lt;ffffffff81419a89&gt;] __kmalloc_cache_noprof+0x2f9/0x3f0 [&lt;ffffffff8113f715&gt;] task_numa_work+0x725/0xa00 [&lt;ffffffff8110f878&gt;] task_work_run+0x58/0x90 [&lt;ffffffff81ddd9f8&gt;] syscall_exit_to_user_mode+0x1c8/0x1e0 [&lt;ffffffff81dd78d5&gt;] do_syscall_64+0x85/0x150 [&lt;ffffffff81e0012b&gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e ...</p> <p>This issue can be consistently reproduced on three different servers: * a 448-core server * a 256-core server * a 192-core server</p> <p>[Root Cause] Since multiple threads are created by the hackbench program (along with the command argument &#39;thread&#39;), a shared vma…</p> https://vulnerability.circl.lu/vuln/cve-2024-56613