{"id":"CVE-2026-68171","aliases":["DEBIAN-CVE-2026-68171","EUVD-2026-55557","GHSA-r2jg-pf44-vfj6","MGASA-2026-0336","MGASA-2026-0337"],"status":"rejected","title":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: syscall: Ensure saved...","description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-08-10T11:59:40Z","modified":"2026-10-16T15:10:00Z","fixes":[{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.6.148","6.12.101","6.18.42","7.1.6"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.8.0"},{"fixed":"6.6.148"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.101"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.42"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.6"}]}]},{"source":"osv","ecosystem":"Mageia:10","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.44-1.mga10"}]}],"bundled":367},{"source":"osv","ecosystem":"Mageia:10","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.30-4.mga10"}]}],"bundled":367},{"source":"osv","ecosystem":"Mageia:10","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.14-30.mga10"}]}],"bundled":367},{"source":"osv","ecosystem":"Mageia:10","package":"kmod-nvidia-current-wopengpu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"580.173.02-39.mga10.nonfree"}]}],"bundled":367},{"source":"osv","ecosystem":"Mageia:10","package":"drakx-installer-images","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.94-55.mga10.nonfree"}]}],"bundled":367},{"source":"osv","ecosystem":"Mageia:10","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.44-1.mga10"}]}],"bundled":367}],"references":[{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68171","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/64ab0964c7db949abbd3c56268a220e2b77f7b9e","tags":["web"]},{"url":"https://git.kernel.org/stable/c/8000a5f4d1d192f5bb3e4f29e7606a9460d376df","tags":["web"]},{"url":"https://git.kernel.org/stable/c/b7afd2a80593dde3f4a68c9a9f73752f9c340e85","tags":["web"]},{"url":"https://git.kernel.org/stable/c/e057b94772328221405b067c3a85fe479b915dc8","tags":["web"]},{"url":"https://git.kernel.org/stable/c/e59c2476ef755221da31f4e26f6b89712ecf50f1","tags":["web"]},{"url":"https://github.com/advisories/GHSA-r2jg-pf44-vfj6"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68171.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-68171","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0336.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36083","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.40","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.41","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.42","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.43","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.44","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0337.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36084","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-68171","description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","status":"rejected","published":"2026-08-10T11:59:40.623Z","modified":"2026-08-11T02:08:51.173Z","updated_at":"2026-11-02T13:46:10.323375Z"}],"euvd":[{"id":"EUVD-2026-55557","description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","status":"published","published":"2026-08-10T11:59:40Z","modified":"2026-08-11T02:08:51Z","updated_at":"2026-11-02T18:02:00.742322Z"}],"ghsa":[{"id":"GHSA-r2jg-pf44-vfj6","title":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: syscall: Ensure saved...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: syscall: Ensure saved x0 is kept in-sync with tracer updates\n\nWhen seccomp support was originally added to arm64 in a1ae65b21941\n(\"arm64: add seccomp support\"), seccomp was erroneously called _before_\nthe ptrace syscall-enter-stop and therefore the tracer could trivially\nmanipulate the syscall register state after the seccomp check had\npassed. This was subsequently fixed in a5cd110cb836 (\"arm64/ptrace: run\nseccomp after ptrace\") by moving the seccomp check after the tracer has\nrun. Unfortunately, a decade later, that fix has been reported to be\nincomplete.\n\nOn arm64, both the first argument to a syscall and its eventual return\nvalue are allocated to register x0. In order to facilitate syscall\nrestarting and querying of syscall arguments on the syscall exit path,\nthe original value of x0 is stashed in 'struct pt_regs::orig_x0' early\nduring the syscall entry path and is returned for the first argument by\nsyscall_get_arguments(). Unlike 32-bit Arm, this stashed value is not\ndirectly exposed via ptrace() and so changes to register x0 made by the\ntracer on a syscall-enter-stop are not reflected in 'orig_x0'. This\nmeans that seccomp, syscall tracepoints and audit can observe a stale\nvalue for the register compared to the argument that will be observed by\nthe actual syscall.\n\nRe-sync 'orig_x0' from x0 on the syscall entry path following a\npotential ptrace stop (i.e. PTRACE_EVENTMSG_SYSCALL_ENTRY or\nSECCOMP_RET_TRACE). This behaviour is limited to native tasks (because\ncompat tasks expose 'orig_r0' to ptrace) where the syscall is not being\nskipped (because x0 is updated to hold the return value of -ENOSYS in\nthat case).","status":"published","published":"2026-08-10T15:33:39Z","modified":"2026-08-10T15:33:45Z","updated_at":"2026-11-02T15:10:13.54571Z"}],"nvd":[{"id":"CVE-2026-68171","description":"Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","status":"rejected","published":"2026-08-10T13:20:03.78Z","modified":"2026-10-16T15:10:00.103Z","updated_at":"2026-11-02T14:12:35.743275Z"}],"osv":[{"id":"CVE-2026-68171","title":"arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates","description":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: syscall: Ensure saved x0 is kept in-sync with tracer updates\n\nWhen seccomp support was originally added to arm64 in a1ae65b21941\n(\"arm64: add seccomp support\"), seccomp was erroneously called _before_\nthe ptrace syscall-enter-stop and therefore the tracer could trivially\nmanipulate the syscall register state after the seccomp check had\npassed. This was subsequently fixed in a5cd110cb836 (\"arm64/ptrace: run\nseccomp after ptrace\") by moving the seccomp check after the tracer has\nrun. Unfortunately, a decade later, that fix has been reported to be\nincomplete.\n\nOn arm64, both the first argument to a syscall and its eventual return\nvalue are allocated to register x0. In order to facilitate syscall\nrestarting and querying of syscall arguments on the syscall exit path,\nthe original value of x0 is stashed in 'struct pt_regs::orig_x0' early\nduring the syscall entry path and is returned for the first argument by\nsyscall_get_arguments(). Unlike 32-bit Arm, this stashed value is not\ndirectly exposed via ptrace() and so changes to register x0 made by the\ntracer on a syscall-enter-stop are not reflected in 'orig_x0'. This\nmeans that seccomp, syscall tracepoints and audit can observe a stale\nvalue for the register compared to the argument that will be observed by\nthe actual syscall.\n\nRe-sync 'orig_x0' from x0 on the syscall entry path following a\npotential ptrace stop (i.e. PTRACE_EVENTMSG_SYSCALL_ENTRY or\nSECCOMP_RET_TRACE). This behaviour is limited to native tasks (because\ncompat tasks expose 'orig_r0' to ptrace) where the syscall is not being\nskipped (because x0 is updated to hold the return value of -ENOSYS in\nthat case).","status":"published","published":"2026-08-10T11:59:40.623Z","modified":"2026-08-12T04:18:46.321049106Z","updated_at":"2026-11-02T15:45:14.808935Z"},{"id":"DEBIAN-CVE-2026-68171","status":"withdrawn","published":"2026-08-10T13:20:03.78Z","modified":"2026-08-11T08:00:40.507251433Z","updated_at":"2026-11-02T15:46:01.68444Z"},{"id":"MGASA-2026-0336","title":"Updated kernel, kmod-xtables-addons, kmod-virtualbox, kmod-nvidia-current-wopengpu \u0026 drakx-installer-images packages fix security vulnerabilities","description":"Upstream kernel 6.18.44 version fixes bugs and vulnerabilities.\nThe kmod-xtables-addons, kmod-virtualbox, kmod-nvidia-current-wopengpu \u0026\ndrakx-installer-images packages have been updated to work with this new\nkernel.\n","status":"published","published":"2026-08-25T07:50:17Z","modified":"2026-08-26T01:10:06.04000893Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"MGASA-2026-0337","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.18.44 fixes vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-08-25T07:50:17Z","modified":"2026-08-26T01:10:31.902061936Z","updated_at":"2026-11-02T15:49:43.795591Z"}]}}