LiveActive security incident?Get immediate response
CVE Record

CVE-2025-37893: LoongArch: BPF: Fix off-by-one error in build_prologue()

In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Fix off-by-one error in build_prologue() Vincent reported that running BPF progs with tailcalls on LoongArch causes kernel hard lockup. Debugging the issues shows that the JITed image missing a jirl instruction at the end of the epilogue. There are two passes in JIT compiling, the first pass set the flags and the second pass generates JIT code based on those flags. With BPF progs mixing bpf2bpf and tailcalls, build_prologue() generates N insns in the first pass and then generates N+1 insns in the second pass. This makes epilogue_offset off by one and we will jump to some unexpected insn and cause lockup. Fix this by inserting a nop insn.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw on LoongArch systems can make the machine freeze when specially structured BPF programs use both function calls and tail calls. Exploitation requires local access and permission to run relevant BPF programs. The reported outcome is a kernel hard lockup, creating serious availability risk for exposed LoongArch hosts.

Executive priority

Treat affected LoongArch hosts as a high-priority availability issue, especially when local users or workloads can load BPF programs. Patch promptly through supported vendor channels. Systems on other architectures are not identified as exposed by these sources, so confirm architecture before escalating broadly.

Technical view

The LoongArch BPF JIT emits N prologue instructions during its first pass but N+1 during its second for programs mixing bpf2bpf calls and tail calls. This off-by-one epilogue offset can omit the final jirl instruction, redirect execution to an unexpected instruction, and lock the kernel. The published fix inserts a nop to keep pass lengths aligned.

Likely exposure

Exposure is limited to Linux running on LoongArch with the affected BPF JIT path and users able to load relevant BPF programs. The bundle lists affected Linux entries spanning 6.1 through 6.15, but its version boundaries are ambiguous. Other architectures are not identified as affected.

Exploitation context

The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. No active exploitation is established: the bundle marks the CVE absent from KEV and provides no cited exploitation report. The demonstrated behavior is a kernel hard lockup triggered by BPF programs using tail calls.

Researcher notes

CWE-193 accurately reflects the instruction-count off-by-one. The two JIT passes disagree only when bpf2bpf and tail calls are combined, corrupting epilogue placement. Although CVSS scores confidentiality, integrity, and availability impacts as high, the supplied technical description substantiates hard lockup; it does not document data theft, code execution, or public weaponization.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable stable-kernel fix.
  • Confirm downstream distribution backports because package versions may not match upstream numbering.
  • Restrict untrusted users from loading BPF programs where operationally feasible.
  • Prioritize LoongArch systems providing shared, multi-user, or workload execution access.

Validation and detection

  • Inventory Linux hosts and identify those using LoongArch processors.
  • Record kernel package versions and compare them with vendor security guidance.
  • Verify whether each downstream kernel includes one of the referenced stable fixes.
  • Review who can load BPF programs on affected LoongArch hosts.
  • Monitor affected systems for unexplained kernel hangs or watchdog resets.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-193: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-37893 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-37893Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5dc615520c4dfb358245680f1904bad61116648e, 5dc615520c4dfb358245680f1904bad61116648e, 5dc615520c4dfb358245680f1904bad61116648e, 5dc615520c4dfb358245680f1904bad61116648e, 5dc615520c4dfb358245680f1904bad61116648eunaffected
LinuxLinux6.1, 0, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-193 · source CWE mapping

Off-by-one Error

Off-by-one Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.