bpf, cgroup: Fix storage null-ptr-deref after replacing prog
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0c991ebc8c69d29b7fc44db17075c5aa5253e2ab · < 3f562c537e9ecf4bc5e206cfffc2cc047f1b7e94| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf, cgroup: Fix storage null-ptr-deref after replacing prog
Syzkaller reported a storage null-ptr-deref issue after replacing prog. This occurs in the following scenario: 1. prog A, an empty prog, is attached to a cgrp. 2. prog B uses BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE and calls the bpf_get_local_storage helper. 3. link_update is called to replace prog A with prog B.
The reason is that __cgroup_bpf_replace fails to alloc and assign the required cgrp storage for the incoming replacement prog. Consequently, the new prog inherits an uninit storage, leading to null-ptr-deref panic when kick the new prog.
Fix this by rejecting a link update if new_prog's cgroup storage is incompatible with link->prog.
From the CVE record · Linux
The Linux kernel can dereference a null pointer after a cgroup BPF program is replaced with one that uses per-CPU cgroup storage. An attacker able to perform the described BPF link update could trigger a kernel panic when the replacement program runs. The input does not specify network access or user-interaction requirements.
Engineers running Linux kernels that support cgroup BPF program replacement should check their kernel; affected versions are not specified.