CVE-2026-74305

HIGHCVSS 7.8/10EPSS 0.17%

Last modified

CVE-2026-74305 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.17%

7.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= c1c74584b9b4043c52e41fec415226e582d266a3, < 87177497cca90bf4fcfb759eb898560eb5b46a10; >= 66da7cee78590259b400e51a70622ccd41da7bb2, < 1c762d28698483ce7c372091f34d86e4d4828652; >= 7acfa07c585e3d7a64654d38f0a5c762877d0b9b, < eb73056ce2a6f101ddd3bdba89af6b24ebffff85; >= 41688d1fc5d163a6c2c0e95c0419e2cb31a44648, < 9ca06849c4239aa2d580c54651f8588c51cb398b; >= abad3d0bad72a52137e0c350c59542d75ae4f513, < 46fbafe3d2d569d828e8d24a7dbe1659f63685cf; >= abad3d0bad72a52137e0c350c59542d75ae4f513, < cb22dc79528eb26a46d346c3118dbd6b14c70609; >= abad3d0bad72a52137e0c350c59542d75ae4f513, < 10627ddc0167aab5c1c390a10ef461e9937aba08; 19341d5c59e8c7e8528e40f8663e99d67810473c; >= 5.15.192, < 5.15.212; >= 6.1.151, < 6.1.178; >= 6.6.105, < 6.6.145; >= 6.12.46, < 6.12.97; >= 6.16.1, < 6.17
LinuxLinux6.17

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74305?
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.
How severe is CVE-2026-74305?
CVE-2026-74305 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-74305?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-74305?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST