https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 19:30:54 +0000 https://cve.radiocsirt.org/vuln/cve-2025-38383 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/vmalloc: fix data race in show_numa_info()</p> <p>The following data-race was found in show_numa_info():</p> <p>================================================================== BUG: KCSAN: data-race in vmalloc_info_show / vmalloc_info_show</p> <p>read to 0xffff88800971fe30 of 4 bytes by task 8289 on cpu 0: show_numa_info mm/vmalloc.c:4936 [inline] vmalloc_info_show+0x5a8/0x7e0 mm/vmalloc.c:5016 seq_read_iter+0x373/0xb40 fs/seq_file.c:230 proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299 ....</p> <p>write to 0xffff88800971fe30 of 4 bytes by task 8287 on cpu 1: show_numa_info mm/vmalloc.c:4934 [inline] vmalloc_info_show+0x38f/0x7e0 mm/vmalloc.c:5016 seq_read_iter+0x373/0xb40 fs/seq_file.c:230 proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299 ....</p> <p>value changed: 0x0000008f -&gt; 0x00000000 ==================================================================</p> <p>According to this report,there is a read/write data-race because m-&gt;private is accessible to multiple CPUs. To fix this, instead of allocating the heap in proc_vmalloc_init() and passing the heap address to m-&gt;private, vmalloc_info_show() should allocate the heap.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/vmalloc: fix data race in show_numa_info()</p> <p>The following data-race was found in show_numa_info():</p> <p>================================================================== BUG: KCSAN: data-race in vmalloc_info_show / vmalloc_info_show</p> <p>read to 0xffff88800971fe30 of 4 bytes by task 8289 on cpu 0: show_numa_info mm/vmalloc.c:4936 [inline] vmalloc_info_show+0x5a8/0x7e0 mm/vmalloc.c:5016 seq_read_iter+0x373/0xb40 fs/seq_file.c:230 proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299 ....</p> <p>write to 0xffff88800971fe30 of 4 bytes by task 8287 on cpu 1: show_numa_info mm/vmalloc.c:4934 [inline] vmalloc_info_show+0x38f/0x7e0 mm/vmalloc.c:5016 seq_read_iter+0x373/0xb40 fs/seq_file.c:230 proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299 ....</p> <p>value changed: 0x0000008f -&gt; 0x00000000 ==================================================================</p> <p>According to this report,there is a read/write data-race because m-&gt;private is accessible to multiple CPUs. To fix this, instead of allocating the heap in proc_vmalloc_init() and passing the heap address to m-&gt;private, vmalloc_info_show() should allocate the heap.</p> https://cve.radiocsirt.org/vuln/cve-2025-38383