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-89906

LoongArch: BPF: Refactor jump offset calculation in tail call

Description

In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Refactor jump offset calculation in tail call The old macro-based jmp_offset calculation derives the jump distance from a stale prior-pass code stride, which can lead to wrong branch offsets and soft lockups under extra JIT passes. Fix this by calculating the offset directly on the absolute target: "ctx->offset[insn + 1] - ctx->idx". To avoid a false 16-bit range check abort during size estimation, add a "ctx->image == NULL" guard to inject a safe dummy offset.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 35 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-89906, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (11 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 17c010fe45def335fe03a0718935416b04c7f349 – < 50fbc294e4e96246d60cd66f98acf043a362e3a0
    • affected f83d469e16bb1f75991ca67c56786fb2aaa42bea – < 89819868cde78cb2f748533785a46a3430873f20
    • affected cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3 – < 882b8912b7e92341fdb115ba0e2e5142a28684ff
    • affected cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3 – < 96f44d493c280ea161569c43d7ed0f3b0815803a
    • affected cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3 – < 37d545d12f21c4d50612ecaebd7ae1e5bf91b2d8
    • affected 1a782fa32e644aa9fbae6c8488f3e61221ac96e1
    • affected f2b5e50cc04d7a049b385bc1c93b9cbf5f10c94f
    • affected 9262e3e04621558e875eb5afb5e726b648cd5949
    • affected 6.6.103 – < 6.6.160
    • affected 6.12.43 – < 6.12.114
    • affected 6.1.149 – < 6.2
    • affected 6.15.11 – < 6.16
    • affected 6.16.2 – < 6.17
  • Linux · Linux

    • affected 6.17
    • unaffected < 6.17
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .