bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed
Summary
| CVE | CVE-2026-90313 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:17:29 UTC |
| Updated | 2026-09-17 17:17:29 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed
A potential invalid storage access issue can occur after replacing a
cgroup bpf prog.
This occurs in the following scenario:
1. prog1 with storage is attached to a cgroup in multi-attach mode.
2. prog1 is replaced with prog2 using BPF_F_REPLACE in multi-attach
mode, but fails midway (e.g. in bpf_trampoline_link_cgroup_shim or
update_effective_progs).
3. A new prog3 is attached to the cgroup in multi-attach mode.
The reason is that __cgroup_bpf_attach overwrites pl->storage with the
new storage prior to attachment completion. When attachment fails
midway, the cleanup path calls bpf_cgroup_storages_free(new_storage) to
free the newly allocated storage, but fails to restore pl->storage back
to old_storage.
Consequently, the still-active prog1 holds invalid or dangling storage
pointers, leading to an invalid memory access when prog1 executes and
calls bpf_get_local_storage. Additionally, original pl->flags and
cgrp->bpf.flags[atype] are left unrestored.
Fix this by saving old_pl_flags, old_storage, and old_flags prior to the
update, and properly restoring all of them in the cleanup path on error. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 e26db0d636e4c24a6b16683ea95cf5077c64d74b git |
Not specified |
| CNA |
Linux |
Linux |
affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 aaca16e042527f7efe48b50799bc662f1a191ce1 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 86ead176301109b78e1d14c0e9d0d9ff9723c769 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 2c2218560b6e28a63ff7834ba26d09ff8efdee39 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 6655c409707ec8ce9ce0850ffe4fe02331fd4d9c git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.9 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.9 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/86ead176301109b78e1d14c0e9d0d9ff9723c769 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/aaca16e042527f7efe48b50799bc662f1a191ce1 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6655c409707ec8ce9ce0850ffe4fe02331fd4d9c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2c2218560b6e28a63ff7834ba26d09ff8efdee39 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e26db0d636e4c24a6b16683ea95cf5077c64d74b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.