CVE-2026-72427

CVE CVE-2026-72427EUVD EUVD-2026-59326Published 2026-08-15T05:56:44.000ZLast changed 2026-08-17T05:44:07.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix effective prog array index with BPF_F_PREORDER replace_effective_prog() and purge_effective_progs() located the slot in the effective array by walking the program hlist and counting entries linearly. That count does not match the array layout: compute_effective_ progs() places BPF_F_PREORDER programs at the front (ancestor cgroup first, attach order within a cgroup) and the rest after them (descendant cgroup first). So when a preorder program is present, the linear hlist position no longer equals the program's index in the effective array. For replace_effective_prog() (bpf_link_update()) this overwrote the wrong slot, corrupting the effective order. For purge_effective_progs(), it could dummy out a slot belonging to a different program and leave the detached program in the array while bpf_prog_put() drops its reference, i.e. a use-after-free. Fix both by replaying compute_effective_progs()'s placement (including the per-cgroup preorder reversal) in a shared effective_prog_pos() helper. Identify the entry by its struct bpf_prog_list pointer rather than by (prog, link) value, so the lookup resolves to exactly the attachment the syscall selected even when the same bpf_prog is attached to several cgroups in the hierarchy.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 555c0b713ca83968d3c843cb15485b9ba3367b1b <41b4320b84fdafe1ab586b06453d30d50415db59; 6.12.31 <6.12.97; patch: 6.12.97; 4b82b181a26cff8bf7adc3a85a88d121d92edeaf <9697db03e010391c55ae75192cbdf30c5a72c114; 6.6.93 <6.6.145; 6.15; patch: 0; patch: 7.1.5; patch: 6.18.40; 4b82b181a26cff8bf7adc3a85a88d121d92edeaf <f08aaee3152d0dfc578b3f2586932d82062701dd; 6.14.9 <6.15; patch: 6.6.145; patch: 7.2; 4707ad649cf662add3058bff47430817811b048d; 4b82b181a26cff8bf7adc3a85a88d121d92edeaf <b584f107ab90222bd825dcb4c5977326ff684109; bc8023ef3b11410682e5d4990e05e5bc2d3e1c94 <525e408c27ae714e538b8c608c3a974df3ab6c92

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.