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 80952 i3c master fix info leak and uaf in device
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-80952

i3c: master: Fix info leak and UAF in device unregister pathCVE-2026-80952

Answer in brief

CVE-2026-80952 records a High severity (CVSS 7.8) vulnerability in i3c: master: Fix info leak and UAF in device unregister path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). 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 11, 2026Updated Oct 19, 2026Source checked Oct 27, 2026First seen by HOL Sep 11, 2026Material review Oct 19, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
3 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <94fb9786d67a8f8b899e77381620f86bad94fdf7 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <4837be0f9ac2efe5e83b35a696b6242c473d280c || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <d2c743efd2d1ee64e94324664808f623dd865872c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49, 94fb9786d67a8f8b899e77381620f86bad94fdf7, 4837be0f9ac2efe5e83b35a696b6242c473d280c, d2c743efd2d1ee64e94324664808f623dd865872
Linux/Linuxgeneric5.0Not reported
Linux/Linuxgeneric>=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <334cfb5e285cece5dc49fb3fb8ea9b70b2cb5d7e || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <109995153898454c7795c2c299fd0a0b57456a4b || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <c64daaaba08e490c8347ff60aacac4dd51249f91 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <ef72ff6650c4ebf2b444708d84df66db42f262d9 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <94fb9786d67a8f8b899e77381620f86bad94fdf7 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <4837be0f9ac2efe5e83b35a696b6242c473d280c || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <d2c743efd2d1ee64e94324664808f623dd865872334cfb5e285cece5dc49fb3fb8ea9b70b2cb5d7e, 109995153898454c7795c2c299fd0a0b57456a4b, c64daaaba08e490c8347ff60aacac4dd51249f91, ef72ff6650c4ebf2b444708d84df66db42f262d9, c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49, 94fb9786d67a8f8b899e77381620f86bad94fdf7, 4837be0f9ac2efe5e83b35a696b6242c473d280c, d2c743efd2d1ee64e94324664808f623dd865872

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 c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49; Linux/Linux to 334cfb5e285cece5dc49fb3fb8ea9b70b2cb5d7e if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 11, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 19, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Sep 11, 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
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix info leak and UAF in device unregister path i3c_master_unregister_i3c_devs() clears i3cdev->dev->desc before calling device_unregister(). During device_unregister(), device_del() emits a KOBJ_REMOVE uevent and unbinds the driver while the device descriptor is still expected to be valid. As a result, i3c_device_uevent() and a racing modalias_show() can observe a NULL desc and fall back to an uninitialized stack struct i3c_device_info, leaking kernel stack contents in the generated modalias. Driver .remove() callbacks may also encounter an unexpected NULL desc during unbind. Keep desc valid until device_unregister() has completed. Since device_unregister() drops the device reference and may free the device, take an extra reference with get_device() before unregistering. Clear desc afterwards and release the extra reference with put_device(). This preserves the release-time invariant that desc must be NULL while avoiding both the information leak and a potential use-after-free from writing desc after the device has been released.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 27, 2026
References
8 linked sources
Open source record