All reports
Medium

UBUNTU-CVE-2025-38170

Affected versions

Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1046.49~22.04.1
Fixed version
6.8.0-1046.49~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1051.57~22.04.1
Fixed version
6.8.0-1051.57~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1046.53~22.04.1
Fixed version
6.8.0-1046.53~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1047.50~22.04.2
Fixed version
6.8.0-1047.50~22.04.2
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-100.100~22.04.1
Fixed version
6.8.0-100.100~22.04.1
Affected versions
<6.8.0-1044.44~22.04.1
Fixed version
6.8.0-1044.44~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-100.100.1~22.04.1
Fixed version
6.8.0-100.100.1~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1046.49~22.04.1
Fixed version
6.8.0-1046.49~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1043.44~22.04.1
Fixed version
6.8.0-1043.44~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-100.100~22.04.1
Fixed version
6.8.0-100.100~22.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.14.0-1013.13~24.04.1
Fixed version
6.14.0-1013.13~24.04.1
Affected versions
<6.8.0-1046.49
Fixed version
6.8.0-1046.49
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1046.53
Fixed version
6.8.0-1046.53
Affected versions
<6.14.0-1007.7
Fixed version
6.14.0-1007.7
Affected versions
<6.8.0-1039.42
Fixed version
6.8.0-1039.42
Affected versions
<6.8.0-1046.52
Fixed version
6.8.0-1046.52
Affected versions
*
Fixed version
Not reported
Affected versions
<6.14.0-1016.17~24.04.1
Fixed version
6.14.0-1016.17~24.04.1
Affected versions
<6.8.0-1047.50
Fixed version
6.8.0-1047.50
Affected versions
<6.8.0-1043.48
Fixed version
6.8.0-1043.48
Affected versions
<6.8.0-1030.33
Fixed version
6.8.0-1030.33
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1044.44
Fixed version
6.8.0-1044.44
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-100.100.1
Fixed version
6.8.0-100.100.1
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1046.49.1
Fixed version
6.8.0-1046.49.1
Affected versions
<6.8.0-1020.20
Fixed version
6.8.0-1020.20
Affected versions
<6.8.0-1046.49
Fixed version
6.8.0-1046.49
Affected versions
*
Fixed version
Not reported
Affected versions
<6.14.0-1012.12
Fixed version
6.14.0-1012.12
Affected versions
*
Fixed version
Not reported
Affected versions
<6.14.0-1013.13~24.04.1
Fixed version
6.14.0-1013.13~24.04.1
Affected versions
<6.8.0-1043.44
Fixed version
6.8.0-1043.44
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1047.51
Fixed version
6.8.0-1047.51
Affected versions
*
Fixed version
Not reported
Affected versions
<6.14.0-32.32.1~24.04.1
Fixed version
6.14.0-32.32.1~24.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1023.24
Fixed version
6.8.0-1023.24
Affected versions
<6.8.0-100.100
Fixed version
6.8.0-100.100
Affected versions
*
Fixed version
Not reported
Affected versions
<6.8.0-1016.20
Fixed version
6.8.0-1016.20
Affected versions
<6.8.0-1046.49+fips1
Fixed version
6.8.0-1046.49+fips1
Affected versions
<6.8.0-1046.52+fips1
Fixed version
6.8.0-1046.52+fips1
Affected versions
<6.8.0-100.100+fips1
Fixed version
6.8.0-100.100+fips1
Affected versions
<6.8.0-1047.50+fips1
Fixed version
6.8.0-1047.50+fips1
Affected versions
<6.8.1-1041.42~22.04.1
Fixed version
6.8.1-1041.42~22.04.1
Affected versions
<6.8.0-2037.38
Fixed version
6.8.0-2037.38
Affected versions
<6.14.0-1012.12~24.04.1
Fixed version
6.14.0-1012.12~24.04.1
Affected versions
<6.8.1-1041.42
Fixed version
6.8.1-1041.42

Description

In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: Discard stale CPU state when handling SME traps The logic for handling SME traps manipulates saved FPSIMD/SVE/SME state incorrectly, and a race with preemption can result in a task having TIF_SME set and TIF_FOREIGN_FPSTATE clear even though the live CPU state is stale (e.g. with SME traps enabled). This can result in warnings from do_sme_acc() where SME traps are not expected while TIF_SME is set: | /* With TIF_SME userspace shouldn't generate any traps */ | if (test_and_set_thread_flag(TIF_SME)) | WARN_ON(1); This is very similar to the SVE issue we fixed in commit: 751ecf6afd6568ad ("arm64/sve: Discard stale CPU state when handling SVE traps") The race can occur when the SME trap handler is preempted before and after manipulating the saved FPSIMD/SVE/SME state, starting and ending on the same CPU, e.g. | void do_sme_acc(unsigned long esr, struct pt_regs regs) | { | // Trap on CPU 0 with TIF_SME clear, SME traps enabled | // task->fpsimd_cpu is 0. | // per_cpu_ptr(&fpsimd_last_state, 0) is task. | | ... | | // Preempted; migrated from CPU 0 to CPU 1. | // TIF_FOREIGN_FPSTATE is set. | | get_cpu_fpsimd_context(); | | / With TIF_SME userspace shouldn't generate any traps */ | if (test_and_set_thread_flag(TIF_SME)) | WARN_ON(1); | | if (!test_thread_flag(TIF_FOREIGN_FPSTATE)) { | unsigned long vq_minus_one = | sve_vq_from_vl(task_get_sme_vl(current)) - 1; | sme_set_vq(vq_minus_one); | | fpsimd_bind_task_to_cpu(); | } | | put_cpu_fpsimd_context(); | | // Preempted; migrated from CPU 1 to CPU 0. | // task->fpsimd_cpu is still 0 | // If per_cpu_ptr(&fpsimd_last_state, 0) is still task then: | // - Stale HW state is reused (with SME traps enabled) | // - TIF_FOREIGN_FPSTATE is cleared | // - A return to userspace skips HW state restore | } Fix the case where the state is not live and TIF_FOREIGN_FPSTATE is set by calling fpsimd_flush_task_state() to detach from the saved CPU state. This ensures that a subsequent context switch will not reuse the stale CPU state, and will instead set TIF_FOREIGN_FPSTATE, forcing the new state to be reloaded from memory prior to a return to userspace. Note: this was originallly posted as [1]. [ Rutland: rewrite commit message ]

Links