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 90013 tracing take tracearray reference when opening
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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 7.8CVE-2026-90013

tracing: Take trace_array reference when opening options fileCVE-2026-90013

Answer in brief

CVE-2026-90013 records a High severity (CVSS 7.8) vulnerability in tracing: Take trace_array reference when opening options file. 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 16, 2026Updated Oct 30, 2026Source checked Oct 31, 2026First seen by HOL Sep 16, 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
Oct 31, 2026
References
6 linked sources
Open source record

Key facts

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

Why this deserves its current priority

CVSS is 7.8. 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>=577b785f55168d5acb3d123ba41bfe8d7981e044 <97ceaffbd672449ad7ead5ae8788dce16374b0c1 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b7397ceaffbd672449ad7ead5ae8788dce16374b0c1, d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73
Linux/Linuxgeneric2.6.30Not reported
Linux/Linuxgeneric>=577b785f55168d5acb3d123ba41bfe8d7981e044 <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73
Linux/Linuxgeneric>=577b785f55168d5acb3d123ba41bfe8d7981e044 <8cc9c5a8c559d655c32d2190486e89574c14ff52 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <97ceaffbd672449ad7ead5ae8788dce16374b0c1 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b738cc9c5a8c559d655c32d2190486e89574c14ff52, 97ceaffbd672449ad7ead5ae8788dce16374b0c1, d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73
Linux/Linuxgeneric>=577b785f55168d5acb3d123ba41bfe8d7981e044 <a6e15eadfdb6de30c24ef21b31f39a86359f4ab5 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <8cc9c5a8c559d655c32d2190486e89574c14ff52 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <97ceaffbd672449ad7ead5ae8788dce16374b0c1 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73a6e15eadfdb6de30c24ef21b31f39a86359f4ab5, 8cc9c5a8c559d655c32d2190486e89574c14ff52, 97ceaffbd672449ad7ead5ae8788dce16374b0c1, d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73

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 97ceaffbd672449ad7ead5ae8788dce16374b0c1; Linux/Linux to d0f37d77b9b4b241e0b30ef2562f6353cbda3bec; Linux/Linux to 8cc9c5a8c559d655c32d2190486e89574c14ff52; Linux/Linux to a6e15eadfdb6de30c24ef21b31f39a86359f4ab5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 16, 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 16, 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: tracing: Take trace_array reference when opening options file The options files do not take the trace_array reference for the options they represent. This could cause a use-after-free kernel crash if one of these files is opened by one task and another task removes the instance that the option is for. Because it doesn't take a reference upon opening, it will not stop the removal which will free the options descriptor that is being used. As the options are somewhat dynamic in their creation at boot up, each file represents a flag in the trace_array. The trace_array has an array of indexes to represent each of these flags that is stored in the trace_flags_index array. The address of the index array element is used to pass to the inode->i_private pointer. Then that element is read which holds the index (which represents the flag) and then the index is used to calculate the trace_array descriptor from its trace_flags_index array. One issue is that the index element can not be referenced until the trace_array's reference is taken. To handle this, create a new helper function called: trace_array_options_get() that will iterate all the existing trace_arrays in the ftrace_trace_arrays list (under the trace_types_lock), and compare the passed in address of the index element with the entire array of the trace_array's trace_flags_index array. If it matches, then up the corresponding trace_array's reference and return.

Quoted source text, attributed separately from HOL analysis.