7.8

CVE-2025-38261: riscv: save the SR_SUM status over switches

Modified
AliasesUBUNTU-CVE-2025-38261DEBIAN-CVE-2025-38261CGA-242r-49gp-vfm3
Published 09-07-2025Last modified 30-10-2026

Vulnerability summary

CVE-2025-38261 is a high (CVSS 7.8) vulnerability in linux. EPSS estimates a 0.24% chance of exploitation in the next 30 days, higher than 14.7% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7.8, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.8/10
010
High · v3.1 (CVE.org)
EPSS score
0.24%
0%100%
Low · +0.08 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 6 · Related 7

Timeline

  1. 09-07-2025
    PublishedVulnerability first disclosed.
  2. 30-10-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: riscv: save the SR_SUM status over switches When threads/tasks are switched we need to ensure the old execution's SR_SUM state is saved and the new thread has the old SR_SUM state restored. The issue was seen under heavy load especially with the syz-stress tool running, with crashes as follows in schedule_tail: Unable to handle kernel access to user memory without uaccess routines at virtual address 000000002749f0d0 Oops [#1] Modules linked in: CPU: 1 PID: 4875 Comm: syz-executor.0 Not tainted 5.12.0-rc2-syzkaller-00467-g0d7588ab9ef9 #0 Hardware name: riscv-virtio,qemu (DT) epc : schedule_tail+0x72/0xb2 kernel/sched/core.c:4264 ra : task_pid_vnr include/linux/sched.h:1421 [inline] ra : schedule_tail+0x70/0xb2 kernel/sched/core.c:4264 epc : ffffffe00008c8b0 ra : ffffffe00008c8ae sp : ffffffe025d17ec0 gp : ffffffe005d25378 tp : ffffffe00f0d0000 t0 : 0000000000000000 t1 : 0000000000000001 t2 : 00000000000f4240 s0 : ffffffe025d17ee0 s1 : 000000002749f0d0 a0 : 000000000000002a a1 : 0000000000000003 a2 : 1ffffffc0cfac500 a3 : ffffffe0000c80cc a4 : 5ae9db91c19bbe00 a5 : 0000000000000000 a6 : 0000000000f00000 a7 : ffffffe000082eba s2 : 0000000000040000 s3 : ffffffe00eef96c0 s4 : ffffffe022c77fe0 s5 : 0000000000004000 s6 : ffffffe067d74e00 s7 : ffffffe067d74850 s8 : ffffffe067d73e18 s9 : ffffffe067d74e00 s10: ffffffe00eef96e8 s11: 000000ae6cdf8368 t3 : 5ae9db91c19bbe00 t4 : ffffffc4043cafb2 t5 : ffffffc4043cafba t6 : 0000000000040000 status: 0000000000000120 badaddr: 000000002749f0d0 cause: 000000000000000f Call Trace: [<ffffffe00008c8b0>] schedule_tail+0x72/0xb2 kernel/sched/core.c:4264 [<ffffffe000005570>] ret_from_exception+0x0/0x14 Dumping ftrace buffer: (ftrace buffer empty) ---[ end trace b5f8f9231dc87dda ]--- The issue comes from the put_user() in schedule_tail (kernel/sched/core.c) doing the following: asmlinkage __visible void schedule_tail(struct task_struct *prev) { ... if (current->set_child_tid) put_user(task_pid_vnr(current), current->set_child_tid); ... } the put_user() macro causes the code sequence to come out as follows: 1: __enable_user_access() 2: reg = task_pid_vnr(current); 3: *current->set_child_tid = reg; 4: __disable_user_access() The problem is that we may have a sleeping function as argument which could clear SR_SUM causing the panic above. This was fixed by evaluating the argument of the put_user() macro outside the user-enabled section in commit 285a76bb2cf5 ("riscv: evaluate put_user() arg before enabling user access")" In order for riscv to take advantage of unsafe_get/put_XXX() macros and to avoid the same issue we had with put_user() and sleeping functions we must ensure code flow can go through switch_to() from within a region of code with SR_SUM enabled and come back with SR_SUM still enabled. This patch addresses the problem allowing future work to enable full use of unsafe_get/put_XXX() macros without needing to take a CSR bit flip cost on every access. Make switch_to() save and restore SR_SUM.

CVSS metrics

6 scores · 5 sources · 2 versions

EPSS trend

Probability

0.24%

Chance of exploitation in the next 30 days

Percentile

15%

Versus all other CVEs

30-day change

Increase +0.08 pp

From 0.15% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu148 products
  • linuxAll versions (No fix recorded)
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded)
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard5 products
  • linux-aws-6.12< 6.12.67-r0 | < 6.12.69-r0 | < 6.12.66-r0 | < 6.12.74-r0 | < 6.12.78-r0 | < 6.12.74-r1 | < 6.12.63-r0 | < 6.12.71-r0 | < 6.12.76-r0 | < 6.12.77-r0 | < 6.12.68-r0 | < 6.12.60-r4 | < 6.12.68-r1 | < 6.12.62-r2 | < 6.12.80-r0 | < 6.12.65-r1 | < 6.12.72-r0 | < 6.12.72-r1 | < 6.12.65-r2 | < 6.12.77-r1 | < 6.12.62-r1 | < 6.12.77-r2 | < 6.12.62-r0 | < 6.12.70-r0 | < 6.12.65-r0
  • linux-azure-6.12< 6.12.62-r2 | < 6.12.76-r0 | < 6.12.74-r1 | < 6.12.66-r0 | < 6.12.60-r3 | < 6.12.70-r0 | < 6.12.72-r0 | < 6.12.67-r0 | < 6.12.62-r1 | < 6.12.71-r0 | < 6.12.65-r2 | < 6.12.77-r0 | < 6.12.69-r0 | < 6.12.65-r3 | < 6.12.65-r4 | < 6.12.77-r2 | < 6.12.63-r0 | < 6.12.74-r0 | < 6.12.78-r0 | < 6.12.60-r4 | < 6.12.62-r0 | < 6.12.77-r1 | < 6.12.65-r1 | < 6.12.80-r0 | < 6.12.68-r0
  • linux-gcp-6.12< 6.12.67-r0 | < 6.12.62-r1 | < 6.12.65-r2 | < 6.12.74-r1 | < 6.12.60-r3 | < 6.12.62-r2 | < 6.12.65-r1 | < 6.12.77-r0 | < 6.12.77-r1 | < 6.12.71-r0 | < 6.12.74-r0 | < 6.12.66-r0 | < 6.12.65-r0 | < 6.12.80-r0 | < 6.12.70-r0 | < 6.12.76-r0 | < 6.12.62-r0 | < 6.12.68-r0 | < 6.12.69-r0 | < 6.12.78-r0 | < 6.12.72-r0 | < 6.12.60-r4 | < 6.12.68-r1 | < 6.12.63-r0 | < 6.12.77-r2
  • linux-qemu-6.12< 6.12.66-r0 | < 6.12.74-r1 | < 6.12.69-r0 | < 6.12.77-r0 | < 6.12.77-r2 | < 6.12.70-r0 | < 6.12.76-r0 | < 6.12.78-r0 | < 6.12.80-r0 | < 6.12.74-r0 | < 6.12.72-r0 | < 6.12.68-r0 | < 6.12.67-r0 | < 6.12.65-r1 | < 6.12.77-r1 | < 6.12.65-r2 | < 6.12.71-r0
  • linux-vmware-6.12< 6.12.67-r0 | < 6.12.69-r0 | < 6.12.72-r0 | < 6.12.74-r1 | < 6.12.65-r1 | < 6.12.74-r0 | < 6.12.68-r1 | < 6.12.71-r0 | < 6.12.78-r0 | < 6.12.70-r0 | < 6.12.76-r0 | < 6.12.68-r0 | < 6.12.77-r1 | < 6.12.65-r2 | < 6.12.77-r2 | < 6.12.77-r0 | < 6.12.66-r0 | < 6.12.80-r0
Linux2 products
  • linux≥ 76d2a0493a17d4c8ecc781366850c3c4f8e1a446, < c75dc906eef2a31c18318236f1047c6e0ef4e9dd | ≥ 76d2a0493a17d4c8ecc781366850c3c4f8e1a446, < 1b63cdc0d63ae33522b4714642fbefa298acc274 | ≥ 76d2a0493a17d4c8ecc781366850c3c4f8e1a446, < 9e7005c3638134df5b7df467c1d884a2482c77cb | ≥ 76d2a0493a17d4c8ecc781366850c3c4f8e1a446, < 69ea599a8dab93a620c92c255be4239a06290a77 | ≥ 76d2a0493a17d4c8ecc781366850c3c4f8e1a446, < 788aa64c01f1262310b4c1fb827a36df170d86ea | 4.15
  • linux_kernel≥ 4.15, < 6.15.5
Debian1 product
  • linuxAll versions (No fix recorded) | < 6.12.115-2 | < 6.16.3-1

4 vendors · 156 products

References

18 links
Show all 18 references