arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.191, 6.12.114, 6.18.57, 6.6.160, 7.2.6
- CVEs
- CVE-2026-90347
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:08 UTC · Revision 1
Source evidence
arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
core-osv · Original sourcePublished 17 Sept 2026, 16:08 UTC
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.
osv:CVE-2026-90347
Kernel
Fixed versions: 6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.2.6
Complete source record
{
"id": "226a3a599f4ecc197d81a8a5f245ef975df55ec645af3cf471aace429038dcc3",
"url": "https://osv.dev/vulnerability/CVE-2026-90347",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry",
"summary": "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.",
"evidence": "osv:CVE-2026-90347",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.191",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.160",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.114",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.57",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-90347",
"aliases": [
"CVE-2026-90347"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615"
},
{
"fixed": "a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9"
},
{
"fixed": "332c9c1a148d0425326989c1187face8f6b2a60c"
},
{
"fixed": "ce17c651a90e242ad48df0df89b1e4cebcda5e14"
},
{
"fixed": "e9e2854fcff5733ffc607e8ecc87e0e591ab41fd"
},
{
"fixed": "f433869f23841a50455c4087d85540d5b4d37cde"
},
{
"fixed": "88b839ce497ccb1ff92f7ae742c78dd2937ba572"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90347.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.8.0"
},
{
"fixed": "6.1.191"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.114"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.57"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90347.json"
}
}
],
"modified": "2026-11-01T02:31:01.036702270Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/332c9c1a148d0425326989c1187face8f6b2a60c",
"https://git.kernel.org/stable/c/88b839ce497ccb1ff92f7ae742c78dd2937ba572",
"https://git.kernel.org/stable/c/a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9",
"https://git.kernel.org/stable/c/ce17c651a90e242ad48df0df89b1e4cebcda5e14",
"https://git.kernel.org/stable/c/e9e2854fcff5733ffc607e8ecc87e0e591ab41fd",
"https://git.kernel.org/stable/c/f433869f23841a50455c4087d85540d5b4d37cde",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90347.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-90347",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90347.json"
}
},
"related_cves": [
{
"value": "CVE-2026-90347",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490761,
"published_at": "2026-09-17T16:08:56.232+00:00"
}