CVE-2026-90339
Last modified
CVE-2026-90339 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: powerpc/syscall: Fix syscall skip handling for seccomp and ptrace After enabling GENERIC_ENTRY on PowerPC, syscall_enter_from_user_mode() returns -1 as a sentinel to signal that seccomp or ptrace has intercepted the syscall and already set a return value via syscall_set_return_value(). system_call_exception() was not handling this sentinel, and since -1UL is >= NR_syscalls, the code fell into the out-of-range path and returned -ENOSYS, overwriting the errno already placed in regs->gpr[3]. The naive fix of checking r0 == -1L before the NR_syscalls bounds check is ambiguous: a user legitimately calling syscall(-1) also produces r0 == -1L, and a tracer intercepting such a call would have its injected return value silently discarded. Fix this by introducing a thread flag that is set whenever syscall_set_return_value() explicitly updates the return value. In system_call_exception(), check and clear this flag before dispatching the syscall, and return the preset value directly when it is present. This ensures that an explicitly supplied return value always suppresses syscall execution, regardless of the syscall number. This handles all seccomp actions correctly: - SECCOMP_RET_ERRNO, SECCOMP_RET_TRACE (no tracer), SECCOMP_RET_USER_NOTIF: all call syscall_set_return_value(), flag is set, injected value returned. - SECCOMP_RET_TRAP, SECCOMP_RET_KILL: call syscall_rollback() and deliver a signal; flag is not set, but the process is dying so the return value is irrelevant. The fix covers both ppc32 and ppc64 with no #ifdefs..
Description
In the Linux kernel, the following vulnerability has been resolved: powerpc/syscall: Fix syscall skip handling for seccomp and ptrace After enabling GENERIC_ENTRY on PowerPC, syscall_enter_from_user_mode() returns -1 as a sentinel to signal that seccomp or ptrace has intercepted the syscall and already set a return value via syscall_set_return_value(). system_call_exception() was not handling this sentinel, and since -1UL is >= NR_syscalls, the code fell into the out-of-range path and returned -ENOSYS, overwriting the errno already placed in regs->gpr[3]. The naive fix of checking r0 == -1L before the NR_syscalls bounds check is ambiguous: a user legitimately calling syscall(-1) also produces r0 == -1L, and a tracer intercepting such a call would have its injected return value silently discarded. Fix this by introducing a thread flag that is set whenever syscall_set_return_value() explicitly updates the return value. In system_call_exception(), check and clear this flag before dispatching the syscall, and return the preset value directly when it is present. This ensures that an explicitly supplied return value always suppresses syscall execution, regardless of the syscall number. This handles all seccomp actions correctly: - SECCOMP_RET_ERRNO, SECCOMP_RET_TRACE (no tracer), SECCOMP_RET_USER_NOTIF: all call syscall_set_return_value(), flag is set, injected value returned. - SECCOMP_RET_TRAP, SECCOMP_RET_KILL: call syscall_rollback() and deliver a signal; flag is not set, but the process is dying so the return value is irrelevant. The fix covers both ppc32 and ppc64 with no #ifdefs.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= bee25f97ad24641df55cb3887eb5bfcb2b9d8fbc, < 19b54740e2e1102c7d48553d9e0347c1f6af22b0; >= bee25f97ad24641df55cb3887eb5bfcb2b9d8fbc, < 69cb2be898be6d5826cacd1a628f6945a24480b6 |
| Linux | Linux | 7.2 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90339?
How severe is CVE-2026-90339?
How do I fix CVE-2026-90339?
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 2026
- CVE-2026-90333In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90334In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90335In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90336In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90337In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90338In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9034Use After Free vulnerability in Arm Ltd Bifrost GPU Userspac…7.8
- CVE-2026-90340In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90341In the Linux kernel, the following vulnerability has been re…7.7
- CVE-2026-90342In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90343In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90344In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-90339?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
