What’s Vulnerable › Vulnerabilities

CVE-2022-48714: bpf: Use VM_MAP instead of VM_ALLOC for ringbuf

• Severity: high (CVSS 7.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2024-06-20 · updated 2026-06-17
• Weakness: CWE-125

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

Affected products

• Linux kernel: from 5.8 before 5.10.99; from 5.11 before 5.15.22; from 5.16 before 5.16.8; 5.17-rc1, 5.17-rc2 — fixed in 5.10.99, 5.15.22, 5.16.8

How to fix

Upgrade to a fixed version: Linux kernel 5.10.99, 5.15.22, 5.16.8. Check the vendor advisory for mitigations.

References

• https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb
• https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6
• https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56
• https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c
• https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb
• https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6
• https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56
• https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c

Get alerted when CVE-2022-48714 or the next vulnerability affects your stack