CVE-2026-90099net/sched: account classifier filter allocations to memcg
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: account classifier filter allocations to memcg Allocations in the tc classifier *_change() paths (filter objects, per-CPU counters, and per-filter aux data) use plain GFP_KERNEL without __GFP_ACCOUNT, allowing unprivileged users to pin kernel memory outside memcg charging. The shared tcf_exts_init_ex() action array allocation in cls_api.c was also uncharged; this patch closes it along with the per-classifier filter-object/percpu/aux allocations that remain unaccounted. Add GFP_KERNEL_ACCOUNT to: - the shared tcf_exts_init_ex() action array (cls_api.c), common to every filter of every classifier (32 pointers, 256 bytes); - the filter-object, per-CPU-counter, and per-filter aux allocations in cls_basic, cls_bpf, cls_cgroup, cls_flow, cls_flower, cls_fw, cls_matchall, cls_route and cls_u32; - the u32_init_knode() replace-path knode allocation (cls_u32.c), which allocates the same struct tc_u_knode + sel.keys on every replace of an existing knode and was missed by the create-path-only conversion. Also fix the cls_basic error path: basic_change() inserts fnew into the IDR before allocating the per-CPU counter. If alloc_percpu() fails the errout path kfree'd fnew without idr_remove, leaving a dangling pointer in the IDR. With GFP_KERNEL_ACCOUNT the percpu alloc becomes failable on demand (memcg at memory.max), making the dead path attacker-reachable and burning the handle permanently. Add the idr_remove on the percpu failure path, matching the basic_set_parms failure-path pattern. Note: [email protected] provided a poc for basic_cls, but it was easy to extend to the other classifiers. Conditions to recreate the bug: - CONFIG_NET_SCHED, CONFIG_NET_CLS_* (the classifier being used), CONFIG_NET_CLS_ACT, CONFIG_MEMCG, CONFIG_USER_NS, CONFIG_NET_NS. - Unprivileged user in a fresh user+network namespace (unshare -Urn), or root with CAP_NET_ADMIN. - Create a large number of tc filters (e.g. tc filter add dev lo ingress ... <classifier> ...) while watching a memcg-limited cgroup: system slab grows far faster than memory.current, pinning kernel memory outside memcg charging.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 0da974f4f303a6842516b764507e3c0a03f41e5a – < 8a622d5b4d81c1572f42bbf3fb823b6e63d44dae
- affected 0da974f4f303a6842516b764507e3c0a03f41e5a – < 5fbb06d4f3d4c509ffe95572384a498bf319e5bf
- affected 0da974f4f303a6842516b764507e3c0a03f41e5a – < bf6006cea193cf065f7a64fc7974247f8112af33
- affected 0da974f4f303a6842516b764507e3c0a03f41e5a – < 68fb30607169c92de57c5c82b6af8a733af1cc09
- affected 0da974f4f303a6842516b764507e3c0a03f41e5a – < 18c68c8f3d3ff0a4def1391021b439c4333a6c71
- affected 0da974f4f303a6842516b764507e3c0a03f41e5a – < 1beb81947eb486716af80db7a584f9e9fef7e003
- affected 2.6.18
- unaffected < 2.6.18
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/8a622d5b4d81c1572f42bbf3fb823b6e63d44dae (opens in a new tab)
- https://git.kernel.org/stable/c/5fbb06d4f3d4c509ffe95572384a498bf319e5bf (opens in a new tab)
- https://git.kernel.org/stable/c/bf6006cea193cf065f7a64fc7974247f8112af33 (opens in a new tab)
- https://git.kernel.org/stable/c/68fb30607169c92de57c5c82b6af8a733af1cc09 (opens in a new tab)
- https://git.kernel.org/stable/c/18c68c8f3d3ff0a4def1391021b439c4333a6c71 (opens in a new tab)
- https://git.kernel.org/stable/c/1beb81947eb486716af80db7a584f9e9fef7e003 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81960 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90099)Record last updated .