CVE-2022-48714

  1. Yack CVE
  2. Vulnerabilities (CVE)
  3. CVE-2022-48714

7.1 /10

CVSS v3 : HIGH

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 5.2

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

I

n 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

References
Link Resource
https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb Patch
https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 Patch
https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 Patch
https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c Patch
https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb Patch
https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 Patch
https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 Patch
https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.17:rc2:*:*:*:*:*:*
History

17 Sep 2025, 17:12

Type Values Removed Values Added
CWE CWE-125
CPE cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.17:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
First Time Linux
Linux linux Kernel
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 7.1
References () https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb - () https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb - Patch
References () https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 - () https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 - Patch
References () https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 - () https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 - Patch
References () https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c - () https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c - Patch

21 Nov 2024, 07:33

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb - () https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb -
References () https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 - () https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6 -
References () https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 - () https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56 -
References () https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c - () https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c -

20 Jun 2024, 12:43

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: bpf: use VM_MAP en lugar de VM_ALLOC para ringbuf Después del commit 2fd3fb0be1d1 ("kasan, vmalloc: despoisone las páginas VM_ALLOC después del mapeo"), los mapeos que no sean VM_ALLOC se marcarán como accesibles en __get_vm_area_node( ) cuando KASAN está habilitado. Pero ahora el indicador para el área ringbuf es VM_ALLOC, por lo que KASAN se quejará del acceso fuera de los límites después de que regrese vmap(). Debido a que el área ringbuf se crea asignando páginas asignadas, use VM_MAP en su lugar. Después del cambio, la información en /proc/vmallocinfo también cambia de [inicio]-[fin] 24576 ringbuf_map_alloc+0x171/0x290 usuario vmalloc a [inicio]-[fin] 24576 ringbuf_map_alloc+0x171/0x290 usuario vmap

20 Jun 2024, 11:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-06-20 11:15

Updated : 2025-09-17 17:12

NVD link : CVE-2022-48714

Mitre link : CVE-2022-48714

CVE.ORG link : CVE-2022-48714

JSON object : View

Products Affected

linux

CWE
CWE-125

Out-of-bounds Read