Linux Kernel seccomp filter Vulnerability Rated 8.4 CVSS

Last refreshed2026-10-15

Status: UPDATED | Advisory ID: CVE-2026-90347

Key Details

CVE	CVE-2026-90347
CVSS Score / Version	8.4 (High) / CVSS v3.1
Updated	2026-10-15
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is changed; confidentiality impact is high; integrity impact is high; availability impact is none.
Affected products	Linux Kernel
Exploitation prediction (EPSS)	0.16% probability of exploitation in the next 30 days (5% percentile) -- FIRST.org's EPSS model.

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

In the Linux kernel, the following vulnerability has been resolved:

arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry

Commit e057b9477232 ("arm64: syscall: Ensure saved x0 is kept in-sync

with tracer updates") attempted to resolve a long-standing issue with

syscall entry tracing, where a tracer is able to manipulate the first

syscall argument without being subjected to seccomp or audit checking.

Unfortunately, that fix was incomplete [1], as it failed to update

'orig_x0' between a tracer updating x0 during a seccomp ptrace exit

(SECCOMP_RET_TRACE) and the seccomp filter being re-evaluated.

Rather than add hooks to the core seccomp code, instead move the

synchronisation code into the ptrace GPR and syscall setting code so

that 'orig_x0' is kept up to date with x0 whenever we're stopped on the

syscall entry path. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-90347
CVE	https://www.cve.org/CVERecord?id=CVE-2026-90347

Source

Reference

NVD

CVE