1. Home
  2. Vulnerabilities
  3. CVE-2026-68171
WITHDRAWN
CVE-2026-68171
arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates
Overview
Description

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Details
INFO

Published Date :

Aug. 10, 2026, 1:20 p.m.

Last Modified :

Aug. 11, 2026, 3:18 a.m.

Remotely Exploit :

—

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Impact
Affected Products

The following products are affected by CVE-2026-68171 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-68171 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2026-68171 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 11, 2026

    Action Type Old Value New Value
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 11, 2026

    Action Type Old Value New Value
    Changed Description In the Linux kernel, the following vulnerability has been resolved: arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates When seccomp support was originally added to arm64 in a1ae65b21941 ("arm64: add seccomp support"), seccomp was erroneously called _before_ the ptrace syscall-enter-stop and therefore the tracer could trivially manipulate the syscall register state after the seccomp check had passed. This was subsequently fixed in a5cd110cb836 ("arm64/ptrace: run seccomp after ptrace") by moving the seccomp check after the tracer has run. Unfortunately, a decade later, that fix has been reported to be incomplete. On arm64, both the first argument to a syscall and its eventual return value are allocated to register x0. In order to facilitate syscall restarting and querying of syscall arguments on the syscall exit path, the original value of x0 is stashed in 'struct pt_regs::orig_x0' early during the syscall entry path and is returned for the first argument by syscall_get_arguments(). Unlike 32-bit Arm, this stashed value is not directly exposed via ptrace() and so changes to register x0 made by the tracer on a syscall-enter-stop are not reflected in 'orig_x0'. This means that seccomp, syscall tracepoints and audit can observe a stale value for the register compared to the argument that will be observed by the actual syscall. Re-sync 'orig_x0' from x0 on the syscall entry path following a potential ptrace stop (i.e. PTRACE_EVENTMSG_SYSCALL_ENTRY or SECCOMP_RET_TRACE). This behaviour is limited to native tasks (because compat tasks expose 'orig_r0' to ptrace) where the syscall is not being skipped (because x0 is updated to hold the return value of -ENOSYS in that case). Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
    Removed Reference kernel.org: https://git.kernel.org/stable/c/64ab0964c7db949abbd3c56268a220e2b77f7b9e
    Removed Reference kernel.org: https://git.kernel.org/stable/c/8000a5f4d1d192f5bb3e4f29e7606a9460d376df
    Removed Reference kernel.org: https://git.kernel.org/stable/c/b7afd2a80593dde3f4a68c9a9f73752f9c340e85
    Removed Reference kernel.org: https://git.kernel.org/stable/c/e057b94772328221405b067c3a85fe479b915dc8
    Removed Reference kernel.org: https://git.kernel.org/stable/c/e59c2476ef755221da31f4e26f6b89712ecf50f1
    Removed Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': '8000a5f4d1d192f5bb3e4f29e7606a9460d376df', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': 'b7afd2a80593dde3f4a68c9a9f73752f9c340e85', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': '64ab0964c7db949abbd3c56268a220e2b77f7b9e', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': 'e59c2476ef755221da31f4e26f6b89712ecf50f1', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': 'e057b94772328221405b067c3a85fe479b915dc8', 'versionType': 'git'}], 'programFiles': ['arch/arm64/kernel/ptrace.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.8'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.8', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.148', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc5', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['arch/arm64/kernel/ptrace.c'], 'defaultStatus': 'affected'}]
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 10, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': '8000a5f4d1d192f5bb3e4f29e7606a9460d376df', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': 'b7afd2a80593dde3f4a68c9a9f73752f9c340e85', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': '64ab0964c7db949abbd3c56268a220e2b77f7b9e', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': 'e59c2476ef755221da31f4e26f6b89712ecf50f1', 'versionType': 'git'}, {'status': 'affected', 'version': 'a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615', 'lessThan': 'e057b94772328221405b067c3a85fe479b915dc8', 'versionType': 'git'}], 'programFiles': ['arch/arm64/kernel/ptrace.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.8'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.8', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.148', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc5', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['arch/arm64/kernel/ptrace.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates When seccomp support was originally added to arm64 in a1ae65b21941 ("arm64: add seccomp support"), seccomp was erroneously called _before_ the ptrace syscall-enter-stop and therefore the tracer could trivially manipulate the syscall register state after the seccomp check had passed. This was subsequently fixed in a5cd110cb836 ("arm64/ptrace: run seccomp after ptrace") by moving the seccomp check after the tracer has run. Unfortunately, a decade later, that fix has been reported to be incomplete. On arm64, both the first argument to a syscall and its eventual return value are allocated to register x0. In order to facilitate syscall restarting and querying of syscall arguments on the syscall exit path, the original value of x0 is stashed in 'struct pt_regs::orig_x0' early during the syscall entry path and is returned for the first argument by syscall_get_arguments(). Unlike 32-bit Arm, this stashed value is not directly exposed via ptrace() and so changes to register x0 made by the tracer on a syscall-enter-stop are not reflected in 'orig_x0'. This means that seccomp, syscall tracepoints and audit can observe a stale value for the register compared to the argument that will be observed by the actual syscall. Re-sync 'orig_x0' from x0 on the syscall entry path following a potential ptrace stop (i.e. PTRACE_EVENTMSG_SYSCALL_ENTRY or SECCOMP_RET_TRACE). This behaviour is limited to native tasks (because compat tasks expose 'orig_r0' to ptrace) where the syscall is not being skipped (because x0 is updated to hold the return value of -ENOSYS in that case).
    Added Reference https://git.kernel.org/stable/c/64ab0964c7db949abbd3c56268a220e2b77f7b9e
    Added Reference https://git.kernel.org/stable/c/8000a5f4d1d192f5bb3e4f29e7606a9460d376df
    Added Reference https://git.kernel.org/stable/c/b7afd2a80593dde3f4a68c9a9f73752f9c340e85
    Added Reference https://git.kernel.org/stable/c/e057b94772328221405b067c3a85fe479b915dc8
    Added Reference https://git.kernel.org/stable/c/e59c2476ef755221da31f4e26f6b89712ecf50f1
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CVSS
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.