CVE-2025-37991
Last modified
CVE-2025-37991 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: parisc: Fix double SIGFPE crash Camm noticed that on parisc a SIGFPE exception will crash an application with a second SIGFPE in the signal handler. Dave analyzed it, and it happens because glibc uses a double-word floating-point store to atomically update function descriptors. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: parisc: Fix double SIGFPE crash Camm noticed that on parisc a SIGFPE exception will crash an application with a second SIGFPE in the signal handler. Dave analyzed it, and it happens because glibc uses a double-word floating-point store to atomically update function descriptors. As a result of lazy binding, we hit a floating-point store in fpe_func almost immediately. When the T bit is set, an assist exception trap occurs when when the co-processor encounters *any* floating-point instruction except for a double store of register %fr0. The latter cancels all pending traps. Let's fix this by clearing the Trap (T) bit in the FP status register before returning to the signal handler in userspace. The issue can be reproduced with this test program: root@parisc:~# cat fpe.c static void fpe_func(int sig, siginfo_t *i, void *v) { sigset_t set; sigemptyset(&set); sigaddset(&set, SIGFPE); sigprocmask(SIG_UNBLOCK, &set, NULL); printf("GOT signal %d with si_code %ld\n", sig, i->si_code); } int main() { struct sigaction action = { .sa_sigaction = fpe_func, .sa_flags = SA_RESTART|SA_SIGINFO }; sigaction(SIGFPE, &action, 0); feenableexcept(FE_OVERFLOW); return printf("%lf\n",1.7976931348623158E308*1.7976931348623158E308); } root@parisc:~# gcc fpe.c -lm root@parisc:~# ./a.out Floating point exception root@parisc:~# strace -f ./a.out execve("./a.out", ["./a.out"], 0xf9ac7034 /* 20 vars */) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 ... rt_sigaction(SIGFPE, {sa_handler=0x1110a, sa_mask=[], sa_flags=SA_RESTART|SA_SIGINFO}, NULL, 8) = 0 --- SIGFPE {si_signo=SIGFPE, si_code=FPE_FLTOVF, si_addr=0x1078f} --- --- SIGFPE {si_signo=SIGFPE, si_code=FPE_FLTOVF, si_addr=0xf8f21237} --- +++ killed by SIGFPE +++ Floating point exception
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | < 5.4.294 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.238 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.182 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.138 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.90 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.28 | — |
| Linux | Linux Kernel | >= 6.13, < 6.14.6 | — |
| Linux | Linux Kernel | 6.15 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-37991?
How severe is CVE-2025-37991?
How do I fix CVE-2025-37991?
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-37986In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37987In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37988In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-37989In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3799A vulnerability, which was classified as critical, was found…9.8
- CVE-2025-37990In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37992In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37993In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37994In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37995In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37996In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37997In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-37991?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
