CVE-2022-48714

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2022-48714
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-48714.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2022-48714
Downstream
Related
Published
2024-06-20T11:13:08.007Z
Modified
2026-03-20T12:21:46.157623Z
Summary
bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
Details

In the Linux kernel, the following vulnerability has been resolved:

bpf: Use VMMAP instead of VMALLOC for ringbuf

After commit 2fd3fb0be1d1 ("kasan, vmalloc: unpoison VMALLOC pages after mapping"), non-VMALLOC mappings will be marked as accessible in _getvmareanode() when KASAN is enabled. But now the flag for ringbuf area is VMALLOC, so KASAN will complain out-of-bound access after vmap() returns. Because the ringbuf area is created by mapping allocated pages, so use VMMAP instead.

After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbufmapalloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbufmapalloc+0x171/0x290 vmap user

Database specific 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48714.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
457f44363a8894135c85b7a9afd2bd8196db24ab
Fixed
6304a613a97d6dcd49b93fbad31e9f39d1e138d6
Fixed
5e457aeab52a5947619e1f18047f4d2f3212b3eb
Fixed
d578933f6226d5419af9306746efa1c693cbaf9c
Fixed
b293dcc473d22a62dc6d78de2b15e4f49515db56

Database specific

source 
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-48714.json"