Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-98062, by who scored it
Scored byCVSSScoreVector
NVDNVD · Undergoing Analysis3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 95% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected b2fc4b17fc13810ef440fb323fad3981cd174985 – < 05757377fa0447163d07c43a119f81abe1eef8dc
    • affected 838a10bd2ebfe11a60dd67687533a7cfc220cc86 – < 0e78cb242a57e481061fcb542fed4d51afba25c4
    • affected 838a10bd2ebfe11a60dd67687533a7cfc220cc86 – < d2eaea3599bcce659ce91862254dc91bcbdb6351
    • affected 838a10bd2ebfe11a60dd67687533a7cfc220cc86 – < 77515ab12e4983e6416f8c35039a3f0c0822ac70
    • affected 6.12.6 – < 6.12.114
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98062 badge
[![CVE-2026-98062](https://cveledger.app/badge/CVE-2026-98062.svg)](https://cveledger.app/cve/CVE-2026-98062)

Record last updated .