CVE-2026-89603

CVE CVE-2026-89603EUVD EUVD-2026-76515Published 2026-09-11T19:45:06.000ZLast changed 2026-09-14T12:01:23.000ZCVSS 8.4

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: entry: Fix seccomp bypass after ptrace with TSYNC Sashiko review pointed out the following issue. If a thread is stopped in syscall_trace_enter() for ptrace, another thread can install a seccomp filter with SECCOMP_FILTER_FLAG_TSYNC (e.g., via seccomp_attach_filter()). This will successfully set SYSCALL_WORK_SECCOMP on the stopped thread, but syscall_trace_enter() evaluates a cached 'work' variable sampled on entry. Consequently, the subsequent check for SYSCALL_WORK_SECCOMP misses the newly assigned flag, and the filter is silently bypassed. This race condition could allow an unprivileged process to execute a prohibited system call (e.g., execve) that the newly installed filter was intended to block, especially since the tracer might have modified the system call number during the ptrace stop. Fix this by re-reading the syscall_work flags after ptrace handling, so that any new SYSCALL_WORK_SECCOMP flag set by another thread via TSYNC during the ptrace stop is observed before the subsequent seccomp check.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <23001ee5d8631e30192cde6f6d3ccb6805570499; patch: 6.6.157; patch: 7.3-rc1; 5.9; patch: 6.12.110; 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <22bb836fc133331982c264227a899d4b26a09706; 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <8709e7e1dd7d7de0651e61700edf24f5784f9243; patch: 6.18.51; patch: 5.15.221; patch: 5.10.270; 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <ab4647459098a43e9d6fdb860836f08c962f3774; patch: 6.1.188; 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <459f33f82864723a7fa366cf1091d9c6c893b6b2; 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <eca5ed4200f0be3e91f8a237b1f37582030a93a8; 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <4a3591287fb7f808e209b4974ed337f609a2006b; patch: 0; 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 <09e8880ce5409bdb84da991b053d7087502c181e; patch: 7.2.4

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.