Linux Kernel up to 5.10.98/5.15.21/5.16.7 bpf /proc/vmallocinfo __get_vm_area_node out-of-bounds

Summaryinfo

A vulnerability was found in Linux Kernel up to 5.10.98/5.15.21/5.16.7. It has been classified as problematic. This affects the function __get_vm_area_node of the file /proc/vmallocinfo of the component bpf. The manipulation leads to out-of-bounds. This vulnerability is listed as CVE-2022-48714. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 5.10.98/5.15.21/5.16.7. This issue affects the function __get_vm_area_node of the file /proc/vmallocinfo of the component bpf. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality. The summary by CVE is:

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

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2022-48714. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 209785 (EulerOS Virtualization 2.12.0 : kernel (EulerOS-SA-2024-2781)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.99, 5.15.22 or 5.16.8 eliminates this vulnerability. Applying the patch 6304a613a97d/5e457aeab52a/d578933f6226/b293dcc473d2 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (209785). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.10.0
• 5.10.1
• 5.10.2
• 5.10.3
• 5.10.4
• 5.10.5
• 5.10.6
• 5.10.7
• 5.10.8
• 5.10.9
• 5.10.10
• 5.10.11
• 5.10.12
• 5.10.13
• 5.10.14
• 5.10.15
• 5.10.16
• 5.10.17
• 5.10.18
• 5.10.19
• 5.10.20
• 5.10.21
• 5.10.22
• 5.10.23
• 5.10.24
• 5.10.25
• 5.10.26
• 5.10.27
• 5.10.28
• 5.10.29
• 5.10.30
• 5.10.31
• 5.10.32
• 5.10.33
• 5.10.34
• 5.10.35
• 5.10.36
• 5.10.37
• 5.10.38
• 5.10.39
• 5.10.40
• 5.10.41
• 5.10.42
• 5.10.43
• 5.10.44
• 5.10.45
• 5.10.46
• 5.10.47
• 5.10.48
• 5.10.49
• 5.10.50
• 5.10.51
• 5.10.52
• 5.10.53
• 5.10.54
• 5.10.55
• 5.10.56
• 5.10.57
• 5.10.58
• 5.10.59
• 5.10.60
• 5.10.61
• 5.10.62
• 5.10.63
• 5.10.64
• 5.10.65
• 5.10.66
• 5.10.67
• 5.10.68
• 5.10.69
• 5.10.70
• 5.10.71
• 5.10.72
• 5.10.73
• 5.10.74
• 5.10.75
• 5.10.76
• 5.10.77
• 5.10.78
• 5.10.79
• 5.10.80
• 5.10.81
• 5.10.82
• 5.10.83
• 5.10.84
• 5.10.85
• 5.10.86
• 5.10.87
• 5.10.88
• 5.10.89
• 5.10.90
• 5.10.91
• 5.10.92
• 5.10.93
• 5.10.94
• 5.10.95
• 5.10.96
• 5.10.97
• 5.10.98
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.16.0
• 5.16.1
• 5.16.2
• 5.16.3
• 5.16.4
• 5.16.5
• 5.16.6
• 5.16.7

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion