CVE-2026-93148bpf: Reject MEM_ALLOC BTF accesses past object bounds
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject MEM_ALLOC BTF accesses past object bounds BTF struct walks relax the struct-size check for accesses through a trailing flexible array. That is valid for ordinary BTF type walking, but PTR_TO_BTF_ID | MEM_ALLOC values point to objects allocated with the static BTF type size. When walking a MEM_ALLOC object, reject the access before applying the flexible-array relaxation if the access range extends past the struct size. Apply the same policy to struct ID matching so kfunc and kptr type checks do not walk past the allocated object bounds either.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 958cf2e273f0929c66169e0788031310e8118722 before cf08ff2255de98cfcbc8bf7236fbeb38f0d5b4f1; from 958cf2e273f0929c66169e0788031310e8118722 before e626a50d07d43421cbf7bfb5a084b33a5e276b6e; 958cf2e273f0929c66169e0788031310e8118722 builds before 9c9ee0324c774490ae953162aaaf4561d222bd93 | CNA record |
References
- https://git.kernel.org/stable/c/cf08ff2255de98cfcbc8bf7236fbeb38f0d5b4f1
- https://git.kernel.org/stable/c/e626a50d07d43421cbf7bfb5a084b33a5e276b6e
- https://git.kernel.org/stable/c/9c9ee0324c774490ae953162aaaf4561d222bd93
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.