| Name | CVE-2022-48714 |
| 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 |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| linux (PTS) | jessie, jessie (lts) | 3.16.84-1 | vulnerable |
| stretch (security) | 4.9.320-2 | vulnerable | |
| stretch (lts), stretch | 4.9.320-3 | vulnerable | |
| buster (security), buster, buster (lts) | 4.19.316-1 | fixed | |
| bullseye | 5.10.223-1 | fixed | |
| bullseye (security) | 5.10.226-1 | fixed | |
| bookworm | 6.1.115-1 | fixed | |
| bookworm (security) | 6.1.112-1 | fixed | |
| trixie | 6.11.7-1 | fixed | |
| sid | 6.11.9-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| linux | source | jessie | (unfixed) | end-of-life | ||
| linux | source | stretch | (unfixed) | end-of-life | ||
| linux | source | buster | (not affected) | |||
| linux | source | bullseye | 5.10.103-1 | |||
| linux | source | (unstable) | 5.16.10-1 |
[buster] - linux <not-affected> (Vulnerable code not present)
https://git.kernel.org/linus/b293dcc473d22a62dc6d78de2b15e4f49515db56 (5.17-rc3)