Answer in brief
CVE-2026-90313 records a Unknown severity vulnerability in bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <e26db0d636e4c24a6b16683ea95cf5077c64d74b || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <aaca16e042527f7efe48b50799bc662f1a191ce1 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <86ead176301109b78e1d14c0e9d0d9ff9723c769 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <2c2218560b6e28a63ff7834ba26d09ff8efdee39 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <6655c409707ec8ce9ce0850ffe4fe02331fd4d9c | e26db0d636e4c24a6b16683ea95cf5077c64d74b, aaca16e042527f7efe48b50799bc662f1a191ce1, 86ead176301109b78e1d14c0e9d0d9ff9723c769, 2c2218560b6e28a63ff7834ba26d09ff8efdee39, 6655c409707ec8ce9ce0850ffe4fe02331fd4d9c |
| Linux/Linuxgeneric | 5.9 | Not reported |
| Linux/Linuxgeneric | >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <217b257d2c39e8dc32d691e8952f3cd921a80233 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <e26db0d636e4c24a6b16683ea95cf5077c64d74b || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <aaca16e042527f7efe48b50799bc662f1a191ce1 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <86ead176301109b78e1d14c0e9d0d9ff9723c769 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <2c2218560b6e28a63ff7834ba26d09ff8efdee39 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <6655c409707ec8ce9ce0850ffe4fe02331fd4d9c | 217b257d2c39e8dc32d691e8952f3cd921a80233, e26db0d636e4c24a6b16683ea95cf5077c64d74b, aaca16e042527f7efe48b50799bc662f1a191ce1, 86ead176301109b78e1d14c0e9d0d9ff9723c769, 2c2218560b6e28a63ff7834ba26d09ff8efdee39, 6655c409707ec8ce9ce0850ffe4fe02331fd4d9c |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.