CVE-2026-74305: bpf: Tighten cgroup storage cookie checks for prog arrays
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 10627ddc0167aab5c1c390a10ef461e9937aba08, 1c762d28698483ce7c372091f34d86e4d4828652, 46fbafe3d2d569d828e8d24a7dbe1659f63685cf.
Low priority for now. Upgrade to Linux Linux 10627ddc0167aab5c1c390a10ef461e9937aba08, 1c762d28698483ce7c372091f34d86e4d4828652, 46fbafe3d2d569d828e8d24a7dbe1659f63685cf or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 19341d5c59e8c7e8528e40f8663e99d67810473c, 6.17affected
- c1c74584b9b4043c52e41fec415226e582d266a3 and later · before 87177497cca90bf4fcfb759eb898560eb5b46a10affected · git
- 66da7cee78590259b400e51a70622ccd41da7bb2 and later · before 1c762d28698483ce7c372091f34d86e4d4828652affected · git
- 7acfa07c585e3d7a64654d38f0a5c762877d0b9b and later · before eb73056ce2a6f101ddd3bdba89af6b24ebffff85affected · git
- 41688d1fc5d163a6c2c0e95c0419e2cb31a44648 and later · before 9ca06849c4239aa2d580c54651f8588c51cb398baffected · git
- abad3d0bad72a52137e0c350c59542d75ae4f513 and later · before 46fbafe3d2d569d828e8d24a7dbe1659f63685cfaffected · git
- abad3d0bad72a52137e0c350c59542d75ae4f513 and later · before cb22dc79528eb26a46d346c3118dbd6b14c70609affected · git
- abad3d0bad72a52137e0c350c59542d75ae4f513 and later · before 10627ddc0167aab5c1c390a10ef461e9937aba08affected · git
- 5.15.192 and later · before 5.15.212affected · semver
- 6.1.151 and later · before 6.1.178affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74300Aug 15, 2026 · Bluetooth: hci: validate codec capability element length35Monitor
- ← EarlierCVE-2026-74302Aug 15, 2026 · Bluetooth: hci_core: Fix UAF in hci_unregister_dev()31Monitor
- Later →CVE-2026-74307Aug 15, 2026 · ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 10627ddc0167aab5c1c390a10ef461e9937aba08 | Vendor (CNA) |
| Linux Linux | 1c762d28698483ce7c372091f34d86e4d4828652 | Vendor (CNA) |
| Linux Linux | 46fbafe3d2d569d828e8d24a7dbe1659f63685cf | Vendor (CNA) |
| Linux Linux | 5.15.212 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.12.97 | Vendor (CNA) |
| Linux Linux | 6.17 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 87177497cca90bf4fcfb759eb898560eb5b46a10 | Vendor (CNA) |
| Linux Linux | 9ca06849c4239aa2d580c54651f8588c51cb398b | Vendor (CNA) |
| Linux Linux | cb22dc79528eb26a46d346c3118dbd6b14c70609 | Vendor (CNA) |
| Linux Linux | eb73056ce2a6f101ddd3bdba89af6b24ebffff85 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/1c762d28698483ce7c372091f34d86e4d4828652
- git.kernel.org/stable/c/46fbafe3d2d569d828e8d24a7dbe1659f63685cf
- git.kernel.org/stable/c/87177497cca90bf4fcfb759eb898560eb5b46a10
- git.kernel.org/stable/c/9ca06849c4239aa2d580c54651f8588c51cb398b
- git.kernel.org/stable/c/cb22dc79528eb26a46d346c3118dbd6b14c70609
- git.kernel.org/stable/c/eb73056ce2a6f101ddd3bdba89af6b24ebffff85
Vendor advisories and official records. Exploit/PoC links are deliberately left out.