CVE-2025-37822 [High] | Security Vulnerability in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.04%	0.20%	+0.16%
2	2026-03-21	0.07%	0.04%	-0.03%
3	2026-03-04	—	0.07%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.04%

0.20%

+0.16%

2026-03-21

0.07%

0.04%

-0.03%

2026-03-04

—

0.07%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2025-37822

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-37822 unimportant priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6.	https://security-tracker.debian.org/tracker/CVE-2025-37822
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-37822
`suse`	medium	CVE-2025-37822 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 277 product×package rows across 54 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 15 SP7, … (54 product lines)): Known Not Affected 277.	https://www.suse.com/security/cve/CVE-2025-37822/
`ubuntu`	medium	CVE-2025-37822 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 164, released 132, not-affected 72, needed 35, needs-triage 2, pending 1.	https://ubuntu.com/security/CVE-2025-37822

Affected software / configurations for CVE-2025-37822

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.12, < 6.12.26	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.14.5	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.15	cpe:2.3:o:linux:linux_kernel:6.15:rc1::::::
linux	linux_kernel	6.15	cpe:2.3:o:linux:linux_kernel:6.15:rc2::::::
linux	linux_kernel	6.15	cpe:2.3:o:linux:linux_kernel:6.15:rc3::::::

References for CVE-2025-37822

URL	Tags
https://git.kernel.org/stable/c/1dbb95a36499374c51b47ee8ae258a8862c20978	Patch
https://git.kernel.org/stable/c/77c956152a3a7c7a18b68f3654f70565b2181d03	Patch
https://git.kernel.org/stable/c/7d1d19a11cfbfd8bae1d89cc010b2cc397cd0c48	Patch
https://git.kernel.org/stable/c/b6d8d4d01ca8514fa89b05355f296758a91e2297	Patch
https://git.kernel.org/stable/c/bcf6d3158c5902d92b6d62335af4422b7bf7c4e2	Patch
https://git.kernel.org/stable/c/be6d98766ac952d38241d5a5b213f363afa421c3	Patch

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2025-37822

Common vulnerability scoring system (CVSS) metrics for CVE-2025-37822

Weakness enumeration for CVE-2025-37822

OS Trackers for CVE-2025-37822

Affected software / configurations for CVE-2025-37822

References for CVE-2025-37822