References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Change History

In the Linux kernel, the following vulnerability has been resolved:

bpf: Use VM_MAP instead of VM_ALLOC for ringbuf

After commit 2fd3fb0be1d1 ("kasan, vmalloc: unpoison VM_ALLOC pages
after mapping"), non-VM_ALLOC mappings will be marked as accessible
in __get_vm_area_node() when KASAN is enabled. But now the flag for
ringbuf area is VM_ALLOC, so KASAN will complain out-of-bound access
after vmap() returns. Because the ringbuf area is created by mapping
allocated pages, so use VM_MAP instead.

kernel.org https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb [No types assigned]

kernel.org https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 [No types assigned]

kernel.org https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 [No types assigned]

kernel.org https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c [No types assigned]