CVE-2025-38689
Last modified
CVE-2025-38689 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Fix NULL dereference in avx512_status() Problem ------- With CONFIG_X86_DEBUG_FPU enabled, reading /proc/[kthread]/arch_status causes a warning and a NULL pointer dereference. This is because the AVX-512 timestamp code uses x86_task_fpu() but doesn't check it for NULL. CONFIG_X86_DEBUG_FPU addles that function for kernel threads (PF_KTHREAD specifically), making it return NULL. The point of the warning was to ensure that kernel threads only access task->fpu after going through kernel_fpu_begin()/_end(). EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Fix NULL dereference in avx512_status() Problem ------- With CONFIG_X86_DEBUG_FPU enabled, reading /proc/[kthread]/arch_status causes a warning and a NULL pointer dereference. This is because the AVX-512 timestamp code uses x86_task_fpu() but doesn't check it for NULL. CONFIG_X86_DEBUG_FPU addles that function for kernel threads (PF_KTHREAD specifically), making it return NULL. The point of the warning was to ensure that kernel threads only access task->fpu after going through kernel_fpu_begin()/_end(). Note: all kernel tasks exposed in /proc have a valid task->fpu. Solution -------- One option is to silence the warning and check for NULL from x86_task_fpu(). However, that warning is fairly fresh and seems like a defense against misuse of the FPU state in kernel threads. Instead, stop outputting AVX-512_elapsed_ms for kernel threads altogether. The data was garbage anyway because avx512_timestamp is only updated for user threads, not kernel threads. If anyone ever wants to track kernel thread AVX-512 use, they can come back later and do it properly, separate from this bug fix. [ dhansen: mostly rewrite changelog ]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.16, < 6.16.2 | — |
| Linux | Linux Kernel | 6.17 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-38689?
How severe is CVE-2025-38689?
How do I fix CVE-2025-38689?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38683In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38684In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38685In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38686In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38687In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38688In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-3869The 4stats plugin for WordPress is vulnerable to Cross-Site …6.1
- CVE-2025-38690In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38691In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38692In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38693In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38694In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38689?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
