libbpf: Use OPTS_SET() macro in bpf_xdp_query()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
libbpf: Use OPTS_SET() macro in bpf_xdp_query()
When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds.
The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.
From the CVE record · Linux
Linux libbpf can write beyond the bpf_xdp_query_opts structure when a program compiled against an older libbpf version calls bpf_xdp_query(). This can corrupt the program’s stack. The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux programs compiled against older libbpf versions should check whether those programs call bpf_xdp_query(); affected version numbers were not provided.