bpf: mark a NULL call argument precise
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: mark a NULL call argument precise
check_func_arg() allows bpf_register_is_null() for nullable arguments w/o marking the underlying scalar register precise. Hence a checkpoint created on such a path would prune against arbitrary scalar value.
check_helper_call() enforces second parameter of the bpf_get_local_storage() to be zero, w/o marking the underlying scalar register precise. Hence a checkpoint created on such a path would prune against arbitrary scalar value.
Grouping these two into one patch, as they share the same fixes tag.
From the CVE record · Linux
The Linux kernel BPF verifier can fail to mark certain scalar registers as precise when checking nullable helper arguments or the second argument to bpf_get_local_storage(). This can cause a checkpoint to prune against an arbitrary scalar value. The input does not specify an attacker outcome, access requirements, or user-interaction requirements.
Teams running the Linux kernel should check their versions against the vendor advisory; affected versions are not listed in the input.