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 2025 39841 scsi lpfc fix buffer freeclear order in deferred
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.8CVE-2025-39841

scsi: lpfc: Fix buffer free/clear order in deferred receive pathCVE-2025-39841

Answer in brief

CVE-2025-39841 records a Critical severity (CVSS 9.8) vulnerability in scsi: lpfc: Fix buffer free/clear order in deferred receive path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (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 Sep 19, 2025Updated Oct 19, 2026Source checked Nov 5, 2026First seen by HOL Aug 5, 2026Material review Oct 19, 2026
Upstream Advisory

Key facts

Risk
Critical ยท CVSS 9.8
Exploitation
Not marked as known exploited
Affected software
25 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.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), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.17:rc4:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=472e146d1cf3410a898b49834500fa9e33ac41a2 <ab34084f42ee06a9028d67c78feafb911d33d111 || >=472e146d1cf3410a898b49834500fa9e33ac41a2 <baa39f6ad79d372a6ce0aa639fbb2f1578479f57 || >=472e146d1cf3410a898b49834500fa9e33ac41a2 <95b63d15fce5c54a73bbf195e1aacb5a75b128e2 || >=472e146d1cf3410a898b49834500fa9e33ac41a2 <55658c7501467ca9ef3bd4453dd920010db8bc13 || >=472e146d1cf3410a898b49834500fa9e33ac41a2 <d96cc9a1b57725930c60b607423759d563b4d900 || >=472e146d1cf3410a898b49834500fa9e33ac41a2 <367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11 || >=472e146d1cf3410a898b49834500fa9e33ac41a2 <897f64b01c1249ac730329b83f4f40bab71e86c7 || >=472e146d1cf3410a898b49834500fa9e33ac41a2 <9dba9a45c348e8460da97c450cddf70b2056deb3ab34084f42ee06a9028d67c78feafb911d33d111, baa39f6ad79d372a6ce0aa639fbb2f1578479f57, 95b63d15fce5c54a73bbf195e1aacb5a75b128e2, 55658c7501467ca9ef3bd4453dd920010db8bc13, d96cc9a1b57725930c60b607423759d563b4d900, 367cb5ffd8a8a4c85dc89f55e7fa7cc191425b11, 897f64b01c1249ac730329b83f4f40bab71e86c7, 9dba9a45c348e8460da97c450cddf70b2056deb3
Linux/Linuxgeneric5.1Not reported
Siemens/RUGGEDCOM RST2428Pgeneric>=0 <V3.3V3.3
Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 familygeneric>=0 <V3.3V3.3
Siemens/SCALANCE XCH328generic>=0 <V3.3V3.3
Siemens/SCALANCE XCM324generic>=0 <V3.3V3.3
Siemens/SCALANCE XCM328generic>=0 <V3.3V3.3
Siemens/SCALANCE XCM332generic>=0 <V3.3V3.3
Siemens/SCALANCE XRH334 (24 V DC, 8xFO, CC)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (230 V AC, 12xFO)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (230V AC, 2x10G, 24xSFP, 8xSFP+)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (230 V AC, 8xFO)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (24 V DC, 12xFO)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (24V DC, 2x10G, 24xSFP, 8xSFP+)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (24 V DC, 8xFO)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (2x230 V AC, 12xFO)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (2x230V AC, 2x10G, 24xSFP, 8xSFP+)generic>=0 <V3.3V3.3
Siemens/SCALANCE XRM334 (2x230 V AC, 8xFO)generic>=0 <V3.3V3.3
Siemens/SIMATIC CN 4100generic>=0 <V5.0V5.0

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Siemens/RUGGEDCOM RST2428P.
  2. 2Review the reported fix. Update Linux/Linux to ab34084f42ee06a9028d67c78feafb911d33d111; Siemens/RUGGEDCOM RST2428P to V3.3; Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family to V3.3; Siemens/SCALANCE XCH328 to V3.3; Siemens/SCALANCE XCM324 to V3.3; Siemens/SCALANCE XCM328 to V3.3; Siemens/SCALANCE XCM332 to V3.3; Siemens/SCALANCE XRH334 (24 V DC, 8xFO, CC) to V3.3; Siemens/SCALANCE XRM334 (230 V AC, 12xFO) to V3.3; Siemens/SCALANCE XRM334 (230V AC, 2x10G, 24xSFP, 8xSFP+) to V3.3; Siemens/SCALANCE XRM334 (230 V AC, 8xFO) to V3.3; Siemens/SCALANCE XRM334 (24 V DC, 12xFO) to V3.3; Siemens/SCALANCE XRM334 (24V DC, 2x10G, 24xSFP, 8xSFP+) to V3.3; Siemens/SCALANCE XRM334 (24 V DC, 8xFO) to V3.3; Siemens/SCALANCE XRM334 (2x230 V AC, 12xFO) to V3.3; Siemens/SCALANCE XRM334 (2x230V AC, 2x10G, 24xSFP, 8xSFP+) to V3.3; Siemens/SCALANCE XRM334 (2x230 V AC, 8xFO) to V3.3; Siemens/SIMATIC CN 4100 to V5.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 19, 2025

    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

    Aug 5, 2026

Sources and claim methodology

  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • 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
  • Source referencelists.debian.org
  • Source referencelists.debian.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-after-free window by correcting the buffer release sequence in the deferred receive path. The code freed the RQ buffer first and only then cleared the context pointer under the lock. Concurrent paths (e.g., ABTS and the repost path) also inspect and release the same pointer under the lock, so the old order could lead to double-free/UAF. Note that the repost path already uses the correct pattern: detach the pointer under the lock, then free it after dropping the lock. The deferred path should do the same.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Memory Corruption
EPSS
Not reported
CWE IDs
CWE-787
Source
CVE List V5
Source checked
Nov 5, 2026
References
12 linked sources
Open source record