Answer in brief
CVE-2026-98062 records a Unknown severity vulnerability in bpf: Mark signal tracepoint siginfo arguments as scalar. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=838a10bd2ebfe11a60dd67687533a7cfc220cc86 <0e78cb242a57e481061fcb542fed4d51afba25c4 || >=838a10bd2ebfe11a60dd67687533a7cfc220cc86 <d2eaea3599bcce659ce91862254dc91bcbdb6351 || >=838a10bd2ebfe11a60dd67687533a7cfc220cc86 <77515ab12e4983e6416f8c35039a3f0c0822ac70 || b2fc4b17fc13810ef440fb323fad3981cd174985 || >=6.12.6 <6.13 | 0e78cb242a57e481061fcb542fed4d51afba25c4, d2eaea3599bcce659ce91862254dc91bcbdb6351, 77515ab12e4983e6416f8c35039a3f0c0822ac70, 6.13 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.