https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 20:24:58 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-10964 bdu:2024-10964 https://cve.radiocsirt.org/vuln/bdu:2024-10964 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578 certfr-2024-avi-0578 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578 https://cve.radiocsirt.org/vuln/euvd-2026-310107 EUVD-2026-310107 https://cve.radiocsirt.org/vuln/euvd-2026-310107 https://cve.radiocsirt.org/vuln/fkie_cve-2022-48714 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Use VM_MAP instead of VM_ALLOC for ringbuf</p> <p>After commit 2fd3fb0be1d1 (&#34;kasan, vmalloc: unpoison VM_ALLOC pages after mapping&#34;), 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.</p> <p>After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Use VM_MAP instead of VM_ALLOC for ringbuf</p> <p>After commit 2fd3fb0be1d1 (&#34;kasan, vmalloc: unpoison VM_ALLOC pages after mapping&#34;), 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.</p> <p>After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-48714 https://cve.radiocsirt.org/vuln/ghsa-vfq8-59v7-rr9v <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Use VM_MAP instead of VM_ALLOC for ringbuf</p> <p>After commit 2fd3fb0be1d1 (&#34;kasan, vmalloc: unpoison VM_ALLOC pages after mapping&#34;), 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.</p> <p>After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Use VM_MAP instead of VM_ALLOC for ringbuf</p> <p>After commit 2fd3fb0be1d1 (&#34;kasan, vmalloc: unpoison VM_ALLOC pages after mapping&#34;), 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.</p> <p>After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user</p> https://cve.radiocsirt.org/vuln/ghsa-vfq8-59v7-rr9v https://cve.radiocsirt.org/vuln/suse-su-2024:2372-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:2372-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48714 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 58 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: bpf: Use VM_MAP instead of VM_ALLOC for ringbuf After commit 2fd3fb0be1d1 (&#34;kasan, vmalloc: unpoison VM_ALLOC pages after mapping&#34;), 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. After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 58 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: bpf: Use VM_MAP instead of VM_ALLOC for ringbuf After commit 2fd3fb0be1d1 (&#34;kasan, vmalloc: unpoison VM_ALLOC pages after mapping&#34;), 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. After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48714 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1422 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1422