Skip to main content
Mallory
HighVulnerability

CVE-2025-37822: Missing instruction-cache synchronization in Linux RISC-V uprobes

Published May 8, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.27%20th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2025-37822CWE-662

CVE-2025-37822 affects the Linux kernel's RISC-V uprobes implementation. The execute-out-of-line (XOL) buffer, used to single-step instructions replaced by uprobes, is constructed without the required fence.i instruction-cache synchronization. Consequently, the processor can execute stale or broken instructions instead of the newly constructed instructions. The defect caused unpredictable failures during BPF uprobe selftests on Spacemit K1/X60 hardware.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Affected RISC-V systems can execute incorrect instructions during uprobe single-stepping, causing unreliable behavior, instability, and potential crashes. Specific confidentiality impacts, privilege escalation, or attacker-controlled code execution are not established.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid or limit uprobe-based tracing and BPF uprobe selftests on affected RISC-V systems. Restrict access to BPF loading, probe attachment, and tracing facilities, including CAP_BPF and CAP_SYS_ADMIN where applicable. These measures reduce exposure but do not correct the missing instruction-cache synchronization.

Remediation

Patch, then assume compromise.

Install a vendor-supported Linux kernel update containing the fix that adds instruction-cache synchronization after construction of the RISC-V uprobes XOL buffer, or backport that fix and deploy the patched kernel. For Echo distributions, update the linux package and related packages to version 6.1.164-1 or later.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2025-37822 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2025-37822 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-37822?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2025-37822.
Is there a patch for CVE-2025-37822?
Install a vendor-supported Linux kernel update containing the fix that adds instruction-cache synchronization after construction of the RISC-V uprobes XOL buffer, or backport that fix and deploy the patched kernel. For Echo distributions, update the linux package and related packages to version 6.1.164-1 or later.
What products are affected by CVE-2025-37822?
Linux Kernel.
How severe is CVE-2025-37822?
CVE-2025-37822 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.27% (20th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.