bpf: Explicitly check accesses to bpf_sock_addr
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1cedee13d25ab118d325f95588c1a084e9317229 · < fe9d33f0470350558cb08cecb54cf2267b3a45d2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Explicitly check accesses to bpf_sock_addr
Syzkaller found a kernel warning on the following sock_addr program:
0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit
which triggers:
verifier bug: error during ctx access conversion (0)
This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access.
This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access.
From the CVE record · Linux
The Linux kernel’s BPF sock_addr access check fails to reject an access to padding after msg_src_ip4. A BPF sock_addr program that makes this access can trigger a kernel verifier warning; the input does not specify whether authentication or user interaction is required.
Engineers running the Linux kernel should check for affected versions; none are specified in the input.