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 53224 sctp validate embedded init chunk and address
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
Critical · CVSS 9.1CVE-2026-53224

sctp: validate embedded INIT chunk and address list lengths in cookieCVE-2026-53224

Answer in brief

CVE-2026-53224 records a Critical severity (CVSS 9.1) vulnerability in sctp: validate embedded INIT chunk and address list lengths in cookie. 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 Jun 25, 2026Updated Oct 30, 2026Source checked Nov 4, 2026First seen by HOL Jun 25, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

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

Key facts

Risk
Critical · CVSS 9.1
Exploitation
Not marked as known exploited
Affected software
17 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.1. 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:2.6.12:-:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:2.6.12:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:2.6.12:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:2.6.12:rc4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:2.6.12:rc5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7560afb8cddafd829e709d7ea09230e45a825557 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <512a9bb77c04ac9927648ea58af617e472be96e6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6f4c80a2a7e6d06753b89a578b710a2499a5e62b7560afb8cddafd829e709d7ea09230e45a825557, 512a9bb77c04ac9927648ea58af617e472be96e6, 6f4c80a2a7e6d06753b89a578b710a2499a5e62b
Linux/Linuxgeneric2.6.12Not reported
Linux/Linuxgeneric>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dd75066882ecc4ec8df3f5384b4b9fa9579be8f0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29ab56e7660b6f849c10c46e87e085649df751eb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7560afb8cddafd829e709d7ea09230e45a825557 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <512a9bb77c04ac9927648ea58af617e472be96e6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6f4c80a2a7e6d06753b89a578b710a2499a5e62bdd75066882ecc4ec8df3f5384b4b9fa9579be8f0, 29ab56e7660b6f849c10c46e87e085649df751eb, 7560afb8cddafd829e709d7ea09230e45a825557, 512a9bb77c04ac9927648ea58af617e472be96e6, 6f4c80a2a7e6d06753b89a578b710a2499a5e62b
Linux/Linuxgeneric>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dd75066882ecc4ec8df3f5384b4b9fa9579be8f0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29ab56e7660b6f849c10c46e87e085649df751eb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7560afb8cddafd829e709d7ea09230e45a825557 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <512a9bb77c04ac9927648ea58af617e472be96e6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6f4c80a2a7e6d06753b89a578b710a2499a5e62bb1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0, dd75066882ecc4ec8df3f5384b4b9fa9579be8f0, 29ab56e7660b6f849c10c46e87e085649df751eb, 7560afb8cddafd829e709d7ea09230e45a825557, 512a9bb77c04ac9927648ea58af617e472be96e6, 6f4c80a2a7e6d06753b89a578b710a2499a5e62b

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 7560afb8cddafd829e709d7ea09230e45a825557; Linux/Linux to dd75066882ecc4ec8df3f5384b4b9fa9579be8f0; Linux/Linux to b1ca7dcfb335caa2c73d2d1bb5710e6dea2c11e0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 25, 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 25, 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: sctp: validate embedded INIT chunk and address list lengths in cookie sctp_unpack_cookie() only checked that the embedded INIT chunk length did not exceed the remaining cookie payload, but did not ensure that the INIT chunk is large enough to contain a complete INIT header. A malformed COOKIE_ECHO can therefore carry a truncated INIT chunk whose length field is smaller than sizeof(struct sctp_init_chunk). Later, sctp_process_init() accesses INIT parameters unconditionally, which may lead to out-of-bounds reads. In addition, raw_addr_list_len is not fully validated against the remaining cookie payload. When cookie authentication is disabled, an attacker can supply an oversized raw_addr_list_len and cause sctp_raw_to_bind_addrs() to read beyond the end of the cookie. The address parser also lacks sufficient bounds checks for parameter headers and lengths, allowing malformed address parameters to trigger out-of-bounds reads. Fix this by: - requiring the embedded INIT chunk length to be at least sizeof(struct sctp_init_chunk); - validating that the INIT chunk and raw address list together fit within the cookie payload; - verifying sufficient data exists for each address parameter header and payload before parsing it. Note that sctp_verify_init() must be called after sctp_unpack_cookie() and before sctp_process_init() when cookie authentication is disabled. This will be addressed in a separate patch.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Inverted memory-permission check in the RTIO syscall verifier allows a user-mode thread to read and write arbitrary kernel memoryAlso CWE-125