LiveActive security incident?Get immediate response
CVE Record

CVE-2025-37822: riscv: uprobes: Add missing fence.i after building the XOL buffer

In the Linux kernel, the following vulnerability has been resolved: riscv: uprobes: Add missing fence.i after building the XOL buffer The XOL (execute out-of-line) buffer is used to single-step the replaced instruction(s) for uprobes. The RISC-V port was missing a proper fence.i (i$ flushing) after constructing the XOL buffer, which can result in incorrect execution of stale/broken instructions. This was found running the BPF selftests "test_progs: uprobe_autoattach, attach_probe" on the Spacemit K1/X60, where the uprobes tests randomly blew up.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw on RISC-V systems can cause uprobes, a tracing and debugging feature, to execute outdated or malformed instructions. This may crash workloads or produce incorrect execution. The supplied CVSS score is 7.8 because a local, low-privileged user may trigger serious confidentiality, integrity, and availability consequences.

Executive priority

Treat this as a high-priority platform update where RISC-V Linux is deployed, especially on multi-user or tracing-heavy systems. Organizations without RISC-V assets have low practical exposure. Because exploitation is not documented, prioritize confirmed vulnerable assets rather than initiating an organization-wide emergency response.

Technical view

The RISC-V uprobes implementation constructed execute-out-of-line buffers without issuing fence.i. Consequently, the instruction cache could retain stale contents instead of executing newly written instructions. The issue appeared intermittently during BPF uprobe selftests on Spacemit K1/X60 hardware. Stable-kernel commits in the source bundle add the missing instruction-cache synchronization.

Likely exposure

Exposure is concentrated on RISC-V Linux systems running affected kernel builds where uprobes can be exercised. Systems using other architectures are not implicated by the supplied description. The bundle's affected-version data is ambiguous, so kernel package versions alone may be insufficient; confirm whether the vendor build contains a referenced corrective commit.

Exploitation context

The CVSS vector describes local access, low privileges, low complexity, and no user interaction. However, the supplied sources show only intermittent failures during selftests. CVE-2025-37822 is not listed as KEV in the bundle, and no evidence of active exploitation or a public weaponized exploit is provided.

Researcher notes

The failure concerns instruction-cache coherency after populating the uprobes XOL buffer. Reproduction was reported through the BPF selftests uprobe_autoattach and attach_probe on Spacemit K1/X60. The bundle lists several stable-kernel fixes, but its affected-version entries do not clearly express complete version ranges; validate exposure using vendor package metadata and commit ancestry.

Mitigation direction

  • Update to a vendor-supported RISC-V kernel containing the referenced fence.i correction.
  • Check distribution or appliance vendor guidance for the exact fixed package version.
  • Prioritize shared RISC-V systems where untrusted local users can access tracing capabilities.
  • Apply normal local-access restrictions while awaiting an approved kernel update.

Validation and detection

  • Inventory RISC-V systems and record their running kernel builds.
  • Check vendor changelogs or commit ancestry for a referenced corrective commit.
  • After updating, verify the new kernel is running following reboot.
  • Run approved uprobe and BPF regression tests on representative RISC-V hardware.
  • Monitor affected workloads for tracing-related crashes or incorrect execution.
Prepared
Confidence
medium
Sources
8

Public sources used

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.

cve · low confidence lookup

CVE-2025-37822 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.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

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

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-37822Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux74784081aac8a0f3636965fc230e2d3b7cc123c6, 74784081aac8a0f3636965fc230e2d3b7cc123c6, 74784081aac8a0f3636965fc230e2d3b7cc123c6, 74784081aac8a0f3636965fc230e2d3b7cc123c6, 74784081aac8a0f3636965fc230e2d3b7cc123c6, 74784081aac8a0f3636965fc230e2d3b7cc123c6unaffected
LinuxLinux5.12, 0, 5.15.200, 6.1.163, 6.6.121, 6.12.26, 6.14.5, 6.15affected
Weakness

CWE details

No CWE listed

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