CVE-2026-90313
Last modified
CVE-2026-90313 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 7d9c3427894fe70d1347b4820476bf37736d2ff0, < e26db0d636e4c24a6b16683ea95cf5077c64d74b; >= 7d9c3427894fe70d1347b4820476bf37736d2ff0, < aaca16e042527f7efe48b50799bc662f1a191ce1; >= 7d9c3427894fe70d1347b4820476bf37736d2ff0, < 86ead176301109b78e1d14c0e9d0d9ff9723c769; >= 7d9c3427894fe70d1347b4820476bf37736d2ff0, < 2c2218560b6e28a63ff7834ba26d09ff8efdee39; >= 7d9c3427894fe70d1347b4820476bf37736d2ff0, < 6655c409707ec8ce9ce0850ffe4fe02331fd4d9c |
| Linux | Linux | 5.9 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90313?
How severe is CVE-2026-90313?
How do I fix CVE-2026-90313?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90308In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90309In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-9031An input validation vulnerability exists in the HTTP-WRITEOE…6.8
- CVE-2026-90310Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-90311In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90312In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90314In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90315In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90316In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90317In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90318In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90319In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-90313?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
