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
References
Configurations
Configuration 1 (hide)
|
History
17 Sep 2025, 17:12
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-125 | |
| CPE | cpe:2.3:o:linux:linux_kernel:5.17:rc2:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.1 |
| First Time |
Linux
Linux linux Kernel |
|
| References | () https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb - Patch | |
| References | () https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 - Patch | |
| References | () https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 - Patch | |
| References | () https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c - Patch |
Information
Published : 2024-06-20 11:15
Updated : 2025-09-17 17:12
NVD link : CVE-2022-48714
Mitre link : CVE-2022-48714
CVE.ORG link : CVE-2022-48714
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-125
Out-of-bounds Read
