CVE-2025-38383

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mm/vmalloc: fix data race in show_numa_info()<br /> <br /> The following data-race was found in show_numa_info():<br /> <br /> ==================================================================<br /> BUG: KCSAN: data-race in vmalloc_info_show / vmalloc_info_show<br /> <br /> read to 0xffff88800971fe30 of 4 bytes by task 8289 on cpu 0:<br /> show_numa_info mm/vmalloc.c:4936 [inline]<br /> vmalloc_info_show+0x5a8/0x7e0 mm/vmalloc.c:5016<br /> seq_read_iter+0x373/0xb40 fs/seq_file.c:230<br /> proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299<br /> ....<br /> <br /> write to 0xffff88800971fe30 of 4 bytes by task 8287 on cpu 1:<br /> show_numa_info mm/vmalloc.c:4934 [inline]<br /> vmalloc_info_show+0x38f/0x7e0 mm/vmalloc.c:5016<br /> seq_read_iter+0x373/0xb40 fs/seq_file.c:230<br /> proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299<br /> ....<br /> <br /> value changed: 0x0000008f -&gt; 0x00000000<br /> ==================================================================<br /> <br /> According to this report,there is a read/write data-race because<br /> m-&gt;private is accessible to multiple CPUs. To fix this, instead of<br /> allocating the heap in proc_vmalloc_init() and passing the heap address to<br /> m-&gt;private, vmalloc_info_show() should allocate the heap.