Description
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.
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
Metrics
CVSS 3.1 7.1/10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 457f44363a8894135c85b7a9afd2bd8196db24ab, < 6304a613a97d6dcd49b93fbad31e9f39d1e138d6; >= 457f44363a8894135c85b7a9afd2bd8196db24ab, < 5e457aeab52a5947619e1f18047f4d2f3212b3eb; >= 457f44363a8894135c85b7a9afd2bd8196db24ab, < d578933f6226d5419af9306746efa1c693cbaf9c; >= 457f44363a8894135c85b7a9afd2bd8196db24ab, < b293dcc473d22a62dc6d78de2b15e4f49515db56 |
| Linux | Linux | 5.8 |
References
- https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3ebPatch
- https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6Patch
- https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56Patch
- https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9cPatch
- https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3ebPatch
- https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6Patch
- https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56Patch
- https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9cPatch
Timeline
- Published
- Jun 20, 2024
- Last modified
- Jun 17, 2026
- NVD status
- Analyzed