CVE-2022-48714

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

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Potential Mitigations

• Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
• When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
• Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
• To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/540.html

References

• https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb
• https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6
• https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56
• https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c
• https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb
• https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6
• https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56
• https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c