HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 90347 arm64 ptrace keep origx0 in sync with x0 on
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 8.4CVE-2026-90347

arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entryCVE-2026-90347

Answer in brief

CVE-2026-90347 records a High severity (CVSS 8.4) vulnerability in arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Oct 30, 2026Source checked Nov 2, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Nov 2, 2026
References
6 linked sources
Open source record

Key facts

Risk
High · CVSS 8.4
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <f433869f23841a50455c4087d85540d5b4d37cde || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <88b839ce497ccb1ff92f7ae742c78dd2937ba572f433869f23841a50455c4087d85540d5b4d37cde, 88b839ce497ccb1ff92f7ae742c78dd2937ba572
Linux/Linuxgeneric4.8Not reported
Linux/Linuxgeneric>=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <e9e2854fcff5733ffc607e8ecc87e0e591ab41fd || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <f433869f23841a50455c4087d85540d5b4d37cde || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <88b839ce497ccb1ff92f7ae742c78dd2937ba572e9e2854fcff5733ffc607e8ecc87e0e591ab41fd, f433869f23841a50455c4087d85540d5b4d37cde, 88b839ce497ccb1ff92f7ae742c78dd2937ba572
Linux/Linuxgeneric>=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <332c9c1a148d0425326989c1187face8f6b2a60c || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <ce17c651a90e242ad48df0df89b1e4cebcda5e14 || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <e9e2854fcff5733ffc607e8ecc87e0e591ab41fd || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <f433869f23841a50455c4087d85540d5b4d37cde || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <88b839ce497ccb1ff92f7ae742c78dd2937ba572332c9c1a148d0425326989c1187face8f6b2a60c, ce17c651a90e242ad48df0df89b1e4cebcda5e14, e9e2854fcff5733ffc607e8ecc87e0e591ab41fd, f433869f23841a50455c4087d85540d5b4d37cde, 88b839ce497ccb1ff92f7ae742c78dd2937ba572
Linux/Linuxgeneric>=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9 || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <332c9c1a148d0425326989c1187face8f6b2a60c || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <ce17c651a90e242ad48df0df89b1e4cebcda5e14 || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <e9e2854fcff5733ffc607e8ecc87e0e591ab41fd || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <f433869f23841a50455c4087d85540d5b4d37cde || >=a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 <88b839ce497ccb1ff92f7ae742c78dd2937ba572a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9, 332c9c1a148d0425326989c1187face8f6b2a60c, ce17c651a90e242ad48df0df89b1e4cebcda5e14, e9e2854fcff5733ffc607e8ecc87e0e591ab41fd, f433869f23841a50455c4087d85540d5b4d37cde, 88b839ce497ccb1ff92f7ae742c78dd2937ba572

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to f433869f23841a50455c4087d85540d5b4d37cde; Linux/Linux to e9e2854fcff5733ffc607e8ecc87e0e591ab41fd; Linux/Linux to 332c9c1a148d0425326989c1187face8f6b2a60c; Linux/Linux to a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 30, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Sep 17, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.