PoC Monitor
← All CVEs
CVE-2026-72427published 15 Aug 2026 05:56 UTCData: JSON · API

Linux

bpf: Fix effective prog array index with BPF_F_PREORDER

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= bc8023ef3b11410682e5d4990e05e5bc2d3e1c94, < 525e408c27ae714e538b8c608c3a974df3ab6c92
  • >= 555c0b713ca83968d3c843cb15485b9ba3367b1b, < 41b4320b84fdafe1ab586b06453d30d50415db59
  • >= 4b82b181a26cff8bf7adc3a85a88d121d92edeaf, < 9697db03e010391c55ae75192cbdf30c5a72c114
  • >= 4b82b181a26cff8bf7adc3a85a88d121d92edeaf, < b584f107ab90222bd825dcb4c5977326ff684109
  • >= 4b82b181a26cff8bf7adc3a85a88d121d92edeaf, < f08aaee3152d0dfc578b3f2586932d82062701dd
  • 4707ad649cf662add3058bff47430817811b048d
  • >= 6.6.93, < 6.6.145
  • >= 6.12.31, < 6.12.97
  • >= 6.14.9, < 6.15

Fixed in 525e408c27ae714e538b8c608c3a974df3ab6c92, 41b4320b84fdafe1ab586b06453d30d50415db59, 9697db03e010391c55ae75192cbdf30c5a72c114, b584f107ab90222bd825dcb4c5977326ff684109, f08aaee3152d0dfc578b3f2586932d82062701dd, 6.6.145, 6.12.97, 6.15

Linux Linux
  • 6.15

Fixed in 0, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2

Mitigation

Upgrade Linux to 525e408c27ae714e538b8c608c3a974df3ab6c92 or 41b4320b84fdafe1ab586b06453d30d50415db59 or 9697db03e010391c55ae75192cbdf30c5a72c114 or b584f107ab90222bd825dcb4c5977326ff684109 or f08aaee3152d0dfc578b3f2586932d82062701dd or 6.6.145 or 6.12.97 or 6.15 or later.

Upgrade Linux to 0 or 6.6.145 or 6.12.97 or 6.18.40 or 7.1.5 or 7.2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published15 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.