HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • AI 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.
  • CIGARPoint your coding agent at the right lines and cut its token bill by about a third.

Explore Guard

  • The ChallengePlay the night shift: judge your agent against the real 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.
  • Gauntlet benchmarkGuard tested with real coding agents: safe work runs, risky actions stop.

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 74653 serial 8250of clear stuck empty fifo rx timeout
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

Get HOL Guard for your computer

HOL Guard is a free desktop app that watches what coding agents such as Claude Code, Codex and Cursor run, read and install, and asks you before anything risky happens.

  • Download for macOS
  • Windows download
  • Linux download

Free. macOS 13+ on Apple silicon, Windows x64, Linux AppImage. Other ways to install

Star HOL Guard on GitHub to download
Runs on
macOS 13 or later on Apple silicon, Windows x64 and Linux x86_64.
Price
Free. Paid plans add Guard Cloud for teams. See pricing
Where your data stays
On your computer. Guard Cloud is optional.
Token savings
55.5% to 71.3% fewer tokens across three coding agents in our CIGAR benchmark.

HOL

HOL builds open infrastructure for AI agents: HOL Guard, a directory of AI plugins and MCP servers, an AI agent registry and the open HCS standards.

  • GitHub (opens in a new tab)
  • X (Twitter) (opens in a new tab)
  • YouTube (opens in a new tab)
  • Telegram (opens in a new tab)

HOL Guard

  • What is HOL Guard
  • Features
  • Cut coding agent token costs (CIGAR)
  • Install Guard
  • Download the desktop app
  • Pricing
  • Guard for teams
  • Compare Guard
  • Release notes

Guard for your AI tool

  • Guard for Claude Code
  • Guard for Codex
  • Guard for Cursor
  • Guard for GitHub Copilot CLI
  • Guard for OpenCode
  • Guard for Pi and Oh My Pi
  • Guard for Hermes
  • Guard for OpenClaw
  • All supported AI tools

Research and security

  • Gauntlet: Guard tested with real agents
  • CIGAR token benchmark
  • Research
  • AI security hub
  • Security advisories
  • Active CVEs in AI tools
  • AI agent security guides
  • Extensions and coverage

Plugins and MCP servers

  • Browse AI plugins
  • New plugin launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best Herdr Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins

AI agent registry

  • Best AI agents
  • Best ERC-8004 agents
  • Best Virtuals agents
  • Best A2A agents
  • Best x402 payable agents
  • Submit an ERC-8004 contract
  • Feature your agent

Developers

  • Guard docs
  • Documentation index
  • Developer hub
  • Registry API reference
  • OpenAPI spec
  • Registry OpenAPI spec
  • Run in Postman (opens in a new tab)
  • AI standards ยท HOL Throughline
  • Compare AI standards
  • Collaboration ideas
  • HCS specifications

Company

  • About HOL
  • Blog
  • Contribute to HOL
  • Guard contributors
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact

Copyright ยฉ 2026 HOL DAO LLC. All rights reserved.

  • Privacy
  • Terms of Service
Back to active CVEs
Unknown severity ยท Source severity not reportedCVE-2026-74653

serial: 8250_of: clear stuck empty-FIFO RX-timeout on LPC32xxCVE-2026-74653

Answer in brief

CVE-2026-74653 records a Unknown severity vulnerability in serial: 8250_of: clear stuck empty-FIFO RX-timeout on LPC32xx. 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 Aug 22, 2026Updated Oct 21, 2026Source checked Nov 22, 2026First seen by HOL Aug 22, 2026Material review Oct 21, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3ce24bc4d115336218e59b7e286fd3a79f4fc4c6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7795e8abedc86438cae0454602cbf9038b94bf38 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1423415471274abda87024967d7fe2206ceee0ea || >=0 <6.18.45 || >=0 <7.1.93ce24bc4d115336218e59b7e286fd3a79f4fc4c6, 7795e8abedc86438cae0454602cbf9038b94bf38, 1423415471274abda87024967d7fe2206ceee0ea, 6.18.45, 7.1.9
Linux/Linuxgeneric>=e6e912c4964ce5976e508881207dfa96d5f856d7 <3ce24bc4d115336218e59b7e286fd3a79f4fc4c6 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <7795e8abedc86438cae0454602cbf9038b94bf38 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <1423415471274abda87024967d7fe2206ceee0ea3ce24bc4d115336218e59b7e286fd3a79f4fc4c6, 7795e8abedc86438cae0454602cbf9038b94bf38, 1423415471274abda87024967d7fe2206ceee0ea
Linux/Linuxgeneric2.6.36Not reported
Linux/Linuxgeneric>=e6e912c4964ce5976e508881207dfa96d5f856d7 <c321dc5172c8c66e21ffbeeb7a2ebb88ae6fd4c3 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <3ce24bc4d115336218e59b7e286fd3a79f4fc4c6 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <7795e8abedc86438cae0454602cbf9038b94bf38 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <1423415471274abda87024967d7fe2206ceee0eac321dc5172c8c66e21ffbeeb7a2ebb88ae6fd4c3, 3ce24bc4d115336218e59b7e286fd3a79f4fc4c6, 7795e8abedc86438cae0454602cbf9038b94bf38, 1423415471274abda87024967d7fe2206ceee0ea
Linux/Linuxgeneric>=e6e912c4964ce5976e508881207dfa96d5f856d7 <cc325ce1c40a111824827532ac132afb3d1c342b || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <c321dc5172c8c66e21ffbeeb7a2ebb88ae6fd4c3 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <3ce24bc4d115336218e59b7e286fd3a79f4fc4c6 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <7795e8abedc86438cae0454602cbf9038b94bf38 || >=e6e912c4964ce5976e508881207dfa96d5f856d7 <1423415471274abda87024967d7fe2206ceee0eacc325ce1c40a111824827532ac132afb3d1c342b, c321dc5172c8c66e21ffbeeb7a2ebb88ae6fd4c3, 3ce24bc4d115336218e59b7e286fd3a79f4fc4c6, 7795e8abedc86438cae0454602cbf9038b94bf38, 1423415471274abda87024967d7fe2206ceee0ea

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 3ce24bc4d115336218e59b7e286fd3a79f4fc4c6; Linux/Linux to 3ce24bc4d115336218e59b7e286fd3a79f4fc4c6; Linux/Linux to c321dc5172c8c66e21ffbeeb7a2ebb88ae6fd4c3; Linux/Linux to cc325ce1c40a111824827532ac132afb3d1c342b if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 22, 2026

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

    Oct 21, 2026

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

    Aug 22, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: serial: 8250_of: clear stuck empty-FIFO RX-timeout on LPC32xx The NXP LPC32xx UART (PORT_LPC3220) can latch an RX character-timeout interrupt while the RX FIFO is empty: IIR reports UART_IIR_RX_TIMEOUT (0x0c) but LSR.DR is clear. A character timeout is only cleared by reading RHR, but serial8250_rx_chars() reads RHR only when LSR.DR is set, so nothing ever clears the condition. The interrupt is level-triggered and re-fires immediately, so on a single-core ARM926 the resulting interrupt storm livelocks the CPU. It is reproducible when userspace repeatedly opens the front-panel port (ttyS1): serial8250_do_set_termios() re-enables interrupts on unlock and the handler then spins forever with iir=0xcc lsr=0x60 ier=0x05, tripping the soft-lockup detector in serial8250_handle_irq_locked(). LPC32xx has no dedicated 8250 glue driver, it's driven by the generic 8250_of. Add a hardware specific handle_irq for PORT_LPC3220, wired up in of_platform_serial_setup() the same way fsl8250_handle_irq is installed. The handler follows dw8250_handle_irq(): on an RX timeout with an empty FIFO (LSR.DR and LSR.BI clear) it does one throwaway RHR read to clear the condition, then calls serial8250_handle_irq_locked(). No real received data is ever discarded, and it is a no-op on healthy UARTs which never report a timeout with DR clear. This is the same class of bug already worked around in other 8250 drivers; see commit 424d79183af0 ("serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt") which reports the identical iir=0xcc/lsr=0x60. See also UART_RX_TIMEOUT_QUIRK in 8250_omap, and the note in 8250_bcm7271.

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
Nov 22, 2026
References
5 linked sources
Open source record