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 43353 i3c mipi i3c hci fix race in dma ring dequeue
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-43353

i3c: mipi-i3c-hci: Fix race in DMA ring dequeueCVE-2026-43353

Answer in brief

CVE-2026-43353 records a High severity (CVSS 7.8) vulnerability in i3c: mipi-i3c-hci: Fix race in DMA ring dequeue. 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). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

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

Published May 8, 2026Updated Oct 30, 2026Source checked Nov 4, 2026First seen by HOL Aug 5, 2026Material review Oct 30, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
8 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). 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
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=9ad9a52cce2828d932ae9495181e3d6414f72c07 <b684b420a5bb0ea1b0e13abfdb8ce41c5266e62e || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <4faa1e9c67a2229f6749190aedaf88ce0391efd2 || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <1dca8aee80eea76d2aae21265de5dd64f6ba0f09b684b420a5bb0ea1b0e13abfdb8ce41c5266e62e, 4faa1e9c67a2229f6749190aedaf88ce0391efd2, 1dca8aee80eea76d2aae21265de5dd64f6ba0f09
Linux/Linuxgeneric5.11Not reported
Linux/Linuxgeneric>=9ad9a52cce2828d932ae9495181e3d6414f72c07 <73bb6b15f1fd71479ed12b314876f3ce5935b80a || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <16061383a9def977e4be908c7dcede9a8a4227fd || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <b684b420a5bb0ea1b0e13abfdb8ce41c5266e62e || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <4faa1e9c67a2229f6749190aedaf88ce0391efd2 || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <1dca8aee80eea76d2aae21265de5dd64f6ba0f0973bb6b15f1fd71479ed12b314876f3ce5935b80a, 16061383a9def977e4be908c7dcede9a8a4227fd, b684b420a5bb0ea1b0e13abfdb8ce41c5266e62e, 4faa1e9c67a2229f6749190aedaf88ce0391efd2, 1dca8aee80eea76d2aae21265de5dd64f6ba0f09
Linux/Linuxgeneric>=9ad9a52cce2828d932ae9495181e3d6414f72c07 <d2fa9b855c7b42b34b2fb32731bf533952370384 || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <73bb6b15f1fd71479ed12b314876f3ce5935b80a || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <16061383a9def977e4be908c7dcede9a8a4227fd || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <b684b420a5bb0ea1b0e13abfdb8ce41c5266e62e || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <4faa1e9c67a2229f6749190aedaf88ce0391efd2 || >=9ad9a52cce2828d932ae9495181e3d6414f72c07 <1dca8aee80eea76d2aae21265de5dd64f6ba0f09d2fa9b855c7b42b34b2fb32731bf533952370384, 73bb6b15f1fd71479ed12b314876f3ce5935b80a, 16061383a9def977e4be908c7dcede9a8a4227fd, b684b420a5bb0ea1b0e13abfdb8ce41c5266e62e, 4faa1e9c67a2229f6749190aedaf88ce0391efd2, 1dca8aee80eea76d2aae21265de5dd64f6ba0f09

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 b684b420a5bb0ea1b0e13abfdb8ce41c5266e62e; Linux/Linux to 73bb6b15f1fd71479ed12b314876f3ce5935b80a; Linux/Linux to d2fa9b855c7b42b34b2fb32731bf533952370384 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    May 8, 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

    Aug 5, 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: i3c: mipi-i3c-hci: Fix race in DMA ring dequeue The HCI DMA dequeue path (hci_dma_dequeue_xfer()) may be invoked for multiple transfers that timeout around the same time. However, the function is not serialized and can race with itself. When a timeout occurs, hci_dma_dequeue_xfer() stops the ring, processes incomplete transfers, and then restarts the ring. If another timeout triggers a parallel call into the same function, the two instances may interfere with each other - stopping or restarting the ring at unexpected times. Add a mutex so that hci_dma_dequeue_xfer() is serialized with respect to itself.

Quoted source text, attributed separately from HOL analysis.

Record context

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