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
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 18.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 14.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 16.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 18.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < any | UNKNOWN |
git.kernel.org/linus/b293dcc473d22a62dc6d78de2b15e4f49515db56 (5.17-rc3)
git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb
git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6
git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56
git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c
launchpad.net/bugs/cve/CVE-2022-48714
nvd.nist.gov/vuln/detail/CVE-2022-48714
security-tracker.debian.org/tracker/CVE-2022-48714
www.cve.org/CVERecord?id=CVE-2022-48714