Riskcovery

CVE-2022-48714

bpf: Use VM_MAP instead of VM_ALLOC for ringbuf

State
Published
Severity
Not scored
Published
Jun 20, 2024
Updated
May 11, 2026
Reserved
Jun 20, 2024

Read the record on cve.org

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

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 457f44363a8894135c85b7a9afd2bd8196db24ab to before 6304a613a97d6dcd49b93fbad31e9f39d1e138d6Affected
  • 457f44363a8894135c85b7a9afd2bd8196db24ab to before 5e457aeab52a5947619e1f18047f4d2f3212b3ebAffected
  • 457f44363a8894135c85b7a9afd2bd8196db24ab to before d578933f6226d5419af9306746efa1c693cbaf9cAffected
  • 457f44363a8894135c85b7a9afd2bd8196db24ab to before b293dcc473d22a62dc6d78de2b15e4f49515db56Affected
LinuxLinux
  • 5.8Affected
  • before 5.8Not affected
  • 5.10.99 through 5.10.*Not affected
  • 5.15.22 through 5.15.*Not affected
  • 5.16.8 through 5.16.*Not affected
  • 5.17 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.