All reports
Low

kernel: bpf, cgroup: Fix storage null-ptr-deref after replacing prog

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-90250

Probability of exploitation in the next 30 days: 0.21%

FIRST EPSS · 2026-11-20

Description

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.

A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) cgroup storage mechanism. When replacing an existing BPF program with a new one that uses BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE, the system may fail to properly allocate and assign the necessary cgroup storage. This oversight can lead to a null-pointer dereference, causing a system panic and resulting in a Denial of Service (DoS).