CVE-2026-74305 — bpf: Tighten cgroup storage cookie checks for prog arrays
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ c1c74584b9b4043c52e41fec415226e582d266a3 and < 87177497cca90bf4fcfb759eb898560eb5b46a10≥ 66da7cee78590259b400e51a70622ccd41da7bb2 and < 1c762d28698483ce7c372091f34d86e4d4828652≥ 7acfa07c585e3d7a64654d38f0a5c762877d0b9b and < eb73056ce2a6f101ddd3bdba89af6b24ebffff85≥ 41688d1fc5d163a6c2c0e95c0419e2cb31a44648 and < 9ca06849c4239aa2d580c54651f8588c51cb398b≥ abad3d0bad72a52137e0c350c59542d75ae4f513 and < 46fbafe3d2d569d828e8d24a7dbe1659f63685cf≥ abad3d0bad72a52137e0c350c59542d75ae4f513 and < cb22dc79528eb26a46d346c3118dbd6b14c70609≥ abad3d0bad72a52137e0c350c59542d75ae4f513 and < 10627ddc0167aab5c1c390a10ef461e9937aba08version 19341d5c59e8c7e8528e40f8663e99d67810473c and 6 more≥ 5.15.192 and < 5.15.212≥ 6.1.151 and < 6.1.178≥ 6.6.105 and < 6.6.145≥ 6.12.46 and < 6.12.97≥ 6.16.1 and < 6.17version 6.17 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- git.kernel.org/stable/c/46fbafe3d2d569d828e8d24a7dbe1659f63685cf
- git.kernel.org/stable/c/cb22dc79528eb26a46d346c3118dbd6b14c70609
- git.kernel.org/stable/c/87177497cca90bf4fcfb759eb898560eb5b46a10
- git.kernel.org/stable/c/1c762d28698483ce7c372091f34d86e4d4828652
- git.kernel.org/stable/c/10627ddc0167aab5c1c390a10ef461e9937aba08
- git.kernel.org/stable/c/eb73056ce2a6f101ddd3bdba89af6b24ebffff85
- git.kernel.org/stable/c/9ca06849c4239aa2d580c54651f8588c51cb398b
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 20h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 20h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-74305 is "bpf: Tighten cgroup storage cookie checks for prog arrays", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.