CVE-2026-74305

bpf: Tighten cgroup storage cookie checks for prog arrays

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:58 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Tighten cgroup storage cookie checks for prog arrays The fix in commit abad3d0bad72 ("bpf: Fix oob access in cgroup local storage") is still incomplete. The prog-array compatibility check treats a program with no cgroup storage as compatible with any stored storage cookie. This allows a storage-less program to bridge a tail call chain between an entry program and a storage-using callee even though cgroup local storage at runtime still follows the caller's context, that is, A -> B(no storage) -> C(storage) path. Requiring exact cookie equality would break the legitimate case of a storage-less leaf program being tail called from a storage-using one. Instead, only accept a zero storage cookie if the program cannot perform tail calls itself. This keeps A -> B(no storage) working while rejecting the A -> B(no storage) -> C(storage) bridge.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

19341d5c59e8c7e8528e40f8663e99d67810473c41688d1fc5d163a6c2c0e95c0419e2cb31a446485.15.1926.1.1516.12.466.16.16.176.6.10566da7cee78590259b400e51a70622ccd41da7bb27acfa07c585e3d7a64654d38f0a5c762877d0b9babad3d0bad72a52137e0c350c59542d75ae4f513c1c74584b9b4043c52e41fec415226e582d266a3
Vendor states this is fixed in 10627ddc0167aab5c1c390a10ef461e9937aba08 (fixed)
Vendor states this is fixed in 1c762d28698483ce7c372091f34d86e4d4828652 (fixed)
Vendor states this is fixed in 46fbafe3d2d569d828e8d24a7dbe1659f63685cf (fixed)
Vendor states this is fixed in 87177497cca90bf4fcfb759eb898560eb5b46a10 (fixed)
Vendor states this is fixed in 9ca06849c4239aa2d580c54651f8588c51cb398b (fixed)
Vendor states this is fixed in cb22dc79528eb26a46d346c3118dbd6b14c70609 (fixed)
Vendor states this is fixed in eb73056ce2a6f101ddd3bdba89af6b24ebffff85 (fixed)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card