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 53025 greybus raw fix use after free on cdev close
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
  • Contribute to HOL
  • 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 7.8CVE-2026-53025

greybus: raw: fix use-after-free on cdev closeCVE-2026-53025

Answer in brief

CVE-2026-53025 records a High severity (CVSS 7.8) vulnerability in greybus: raw: fix use-after-free on cdev close. 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 Jun 24, 2026Updated Oct 30, 2026Source checked Nov 4, 2026First seen by HOL Jun 24, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Memory Corruption
EPSS
Not reported
CWE IDs
CWE-416
Source
CVE List V5
Source checked
Nov 4, 2026
References
6 linked sources
Open source record

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
6 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.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <ef2d97c15b19b3489de01695bce478601e236c3e || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <983cc2c7efbce04ecbf6328448d895044dd6ab31ef2d97c15b19b3489de01695bce478601e236c3e, 983cc2c7efbce04ecbf6328448d895044dd6ab31
Linux/Linuxgeneric4.9Not reported
Linux/Linuxgeneric>=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <e72ffe59e48a74a8d9220f5ca1d03f2194d882f0 || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <ef2d97c15b19b3489de01695bce478601e236c3e || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <983cc2c7efbce04ecbf6328448d895044dd6ab31e72ffe59e48a74a8d9220f5ca1d03f2194d882f0, ef2d97c15b19b3489de01695bce478601e236c3e, 983cc2c7efbce04ecbf6328448d895044dd6ab31
Linux/Linuxgeneric>=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <e4d07fd4e30024a4a15094ef2c404197667c857e || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <3abf97a03f4abce1dc3639eea2fcd4bd747b3308 || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <e72ffe59e48a74a8d9220f5ca1d03f2194d882f0 || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <ef2d97c15b19b3489de01695bce478601e236c3e || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <983cc2c7efbce04ecbf6328448d895044dd6ab31e4d07fd4e30024a4a15094ef2c404197667c857e, 3abf97a03f4abce1dc3639eea2fcd4bd747b3308, e72ffe59e48a74a8d9220f5ca1d03f2194d882f0, ef2d97c15b19b3489de01695bce478601e236c3e, 983cc2c7efbce04ecbf6328448d895044dd6ab31
Linux/Linuxgeneric>=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <0597908256173da5256ef8e6db17ccc8d5c40ee3 || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <e4d07fd4e30024a4a15094ef2c404197667c857e || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <3abf97a03f4abce1dc3639eea2fcd4bd747b3308 || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <e72ffe59e48a74a8d9220f5ca1d03f2194d882f0 || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <ef2d97c15b19b3489de01695bce478601e236c3e || >=e806c7fb8e9bae87fc23958c3789f2c2f96f54a4 <983cc2c7efbce04ecbf6328448d895044dd6ab310597908256173da5256ef8e6db17ccc8d5c40ee3, e4d07fd4e30024a4a15094ef2c404197667c857e, 3abf97a03f4abce1dc3639eea2fcd4bd747b3308, e72ffe59e48a74a8d9220f5ca1d03f2194d882f0, ef2d97c15b19b3489de01695bce478601e236c3e, 983cc2c7efbce04ecbf6328448d895044dd6ab31

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 ef2d97c15b19b3489de01695bce478601e236c3e; Linux/Linux to e72ffe59e48a74a8d9220f5ca1d03f2194d882f0; Linux/Linux to e4d07fd4e30024a4a15094ef2c404197667c857e; Linux/Linux to 0597908256173da5256ef8e6db17ccc8d5c40ee3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 24, 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

    Jun 24, 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: greybus: raw: fix use-after-free on cdev close This addresses a use-after-free bug when a raw bundle is disconnected but its chardev is still opened by an application. When the application releases the cdev, it causes the following panic when init on free is enabled (CONFIG_INIT_ON_FREE_DEFAULT_ON=y): refcount_t: underflow; use-after-free. WARNING: CPU: 0 PID: 139 at lib/refcount.c:28 refcount_warn_saturate+0xd0/0x130 ... Call Trace: <TASK> cdev_put+0x18/0x30 __fput+0x255/0x2a0 __x64_sys_close+0x3d/0x80 do_syscall_64+0xa4/0x290 entry_SYSCALL_64_after_hwframe+0x77/0x7f The cdev is contained in the "gb_raw" structure, which is freed in the disconnect operation. When the cdev is released at a later time, cdev_put gets an address that points to freed memory. To fix this use-after-free, convert the struct device from a pointer to being embedded, that makes the lifetime of the cdev and of this device the same. Then, use cdev_device_add, which guarantees that the device won't be released until all references to the cdev have been released. Finally, delegate the freeing of the structure to the device release function, instead of freeing immediately in the disconnect callback.

Quoted source text, attributed separately from HOL analysis.