CVE-2022-48714
bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
- Published
- Updated
- Reserved
- Assigned by
- Linux
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
Timeline
ID reserved
By Linux
Published
- 23 months later
· 23 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Weakness
Affected products
- affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < 6304a613a97d6dcd49b93fbad31e9f39d1e138d6
- affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < 5e457aeab52a5947619e1f18047f4d2f3212b3eb
- affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < d578933f6226d5419af9306746efa1c693cbaf9c
- affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < b293dcc473d22a62dc6d78de2b15e4f49515db56
- affected 5.8
- unaffected < 5.8
- unaffected 5.10.99 – ≤ 5.10.*
- unaffected 5.15.22 – ≤ 5.15.*
- unaffected 5.16.8 – ≤ 5.16.*
- unaffected 5.17 – ≤ *
References (4)
- https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-48714)Record last updated .