CVE-2026-89906

LoongArch: BPF: Refactor jump offset calculation in tail call

HIGH

7.8

CVSS Score

Published: September 16, 2026 at 10:32 AM UTC

Updated: October 21, 2026 at 01:20 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

90%

17c010fe45def335fe03a0718935416b04c7f3491a782fa32e644aa9fbae6c8488f3e61221ac96e16.1.149 6.12.43 6.15.11 6.16.2 6.17 6.6.1039262e3e04621558e875eb5afb5e726b648cd5949cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3f2b5e50cc04d7a049b385bc1c93b9cbf5f10c94ff83d469e16bb1f75991ca67c56786fb2aaa42bea

Vendor states this is fixed in 37d545d12f21c4d50612ecaebd7ae1e5bf91b2d8 (fixed)

Vendor states this is fixed in 882b8912b7e92341fdb115ba0e2e5142a28684ff (fixed)

Vendor states this is fixed in 96f44d493c280ea161569c43d7ed0f3b0815803a (fixed)

Vendor states this is fixed in 6.12.114 (unaffected)

Affected range stops below 6.13, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.16, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.17 (unaffected)

Vendor states this is fixed in 6.18.51 (unaffected)

Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.6.160 (unaffected)

Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 7.2.5 (unaffected)

Vendor states this is fixed in 7.3 (unaffected)

Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (5)

Source: cverecord

https://git.kernel.org/stable/c/882b8912b7e92341fdb115ba0e2e5142a28684ff

Source: cverecord

https://git.kernel.org/stable/c/96f44d493c280ea161569c43d7ed0f3b0815803a

Source: cverecord

https://git.kernel.org/stable/c/37d545d12f21c4d50612ecaebd7ae1e5bf91b2d8

Source: cverecord

https://git.kernel.org/stable/c/50fbc294e4e96246d60cd66f98acf043a362e3a0

Source: cverecord

https://git.kernel.org/stable/c/89819868cde78cb2f748533785a46a3430873f20

CVSS

7.8HIGHLinux

Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card