HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

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.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 74650 staging rtl8723bs fix oob read in wmmparamhandler
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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Unknown severity · Source severity not reportedCVE-2026-74650

staging: rtl8723bs: fix OOB read in WMM_param_handler()CVE-2026-74650

Answer in brief

CVE-2026-74650 records a Unknown severity vulnerability in staging: rtl8723bs: fix OOB read in WMM_param_handler(). 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 Aug 22, 2026Updated Aug 27, 2026Source checked Oct 6, 2026First seen by HOL Aug 22, 2026Material review Aug 27, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
3 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=554c0a3abf216c991c5ebddcdb2c08689ecd290b <6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <2bee6f7a0f0125238951e31da2e96d06fe359043 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <1158b9931207392d6dd136aa0c4be18893b50fa1 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <ce2399717de242344880044b91a20a712644fdfb || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <e5b7610008f4e6a80c8b071aa77ddbd5e17ea472 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <ae21407350151bddfd4fea7aa39bd0643c0ca9d36cdca4c8b64c15a3ab9ad7a85f482e9519eadf93, 2bee6f7a0f0125238951e31da2e96d06fe359043, 1158b9931207392d6dd136aa0c4be18893b50fa1, ce2399717de242344880044b91a20a712644fdfb, e5b7610008f4e6a80c8b071aa77ddbd5e17ea472, e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4, ae21407350151bddfd4fea7aa39bd0643c0ca9d3
Linux/Linuxgeneric4.12Not reported
Linux/Linuxgeneric>=554c0a3abf216c991c5ebddcdb2c08689ecd290b <5df2fd06567df5f178c8faae0bdaefd203618d21 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <2bee6f7a0f0125238951e31da2e96d06fe359043 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <1158b9931207392d6dd136aa0c4be18893b50fa1 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <ce2399717de242344880044b91a20a712644fdfb || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <e5b7610008f4e6a80c8b071aa77ddbd5e17ea472 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4 || >=554c0a3abf216c991c5ebddcdb2c08689ecd290b <ae21407350151bddfd4fea7aa39bd0643c0ca9d35df2fd06567df5f178c8faae0bdaefd203618d21, 6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93, 2bee6f7a0f0125238951e31da2e96d06fe359043, 1158b9931207392d6dd136aa0c4be18893b50fa1, ce2399717de242344880044b91a20a712644fdfb, e5b7610008f4e6a80c8b071aa77ddbd5e17ea472, e429c6dfd5d2324cd866daaf4c29d5cfe4dea0e4, ae21407350151bddfd4fea7aa39bd0643c0ca9d3

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 6cdca4c8b64c15a3ab9ad7a85f482e9519eadf93; Linux/Linux to 5df2fd06567df5f178c8faae0bdaefd203618d21 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

    Aug 27, 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
  • 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: staging: rtl8723bs: fix OOB read in WMM_param_handler() WMM_param_handler() copies a fixed-size WMM parameter element out of a received information element without checking that the element is long enough, causing an out-of-bounds read for a short WMM IE. The handler reads sizeof(struct WMM_para_element) (18) bytes at pIE->data + 6, so it requires pIE->length to be at least 24 (WLAN_WMM_LEN), but it never validates the length. Two of its three callers reach it after matching only the WMM OUI: OnAssocRsp() in rtw_mlme_ext.c matches a 6-byte OUI, and join_cmd_hdl() matches a 4-byte OUI, before calling the handler. A vendor-specific IE carrying the WMM OUI but a length between 6 and 23, placed in an association response or in the IE blob handed to join_cmd_hdl(), passes the OUI check and then makes the memcmp() and memcpy() at pIE->data + 6 read past the end of the element. OnAssocRsp() parses a frame received from the AP, so this is reachable from a remote peer. The remaining caller in rtw_wlan_util.c already guards the handler with "pIE->length == WLAN_WMM_LEN". Move the equivalent check into the handler itself so every caller is covered; the sibling IE handlers in the same parsing loop (HT_caps_handler(), HT_info_handler(), ERP_IE_handler()) likewise bound their accesses by pIE->length.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • SPIP Crayons Plugin < 3.5.0 Authorization Bypass RCESame generic ecosystem
  • Payload: Order confirmation validation issue in Payload EcommerceSame generic ecosystem
  • Payload: Field access control bypass on auth collectionsSame generic ecosystem
  • Payload relationship-query authorization bypassSame generic ecosystem
  • Payload: Token refresh and password reset responses may expose restricted user fieldsSame generic ecosystem
  • Payload: ReDoS in Multipart Content-Type ValidationSame generic ecosystem

Record context

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