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 2024 38780 dma bufsw sync dont enable irq from syncprintobj
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
  • Sponsor
  • Advertise
  • 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-2024-38780

dma-buf/sw-sync: don't enable IRQ from sync_print_obj()CVE-2024-38780

Answer in brief

CVE-2024-38780 records a Unknown severity vulnerability in dma-buf/sw-sync: don't enable IRQ from sync_print_obj(). 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 XCM-/XRM-/XCH-/XRH-300 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 Jun 21, 2024Updated Oct 15, 2026Source checked Oct 15, 2026First seen by HOL Oct 15, 2026Material review Oct 15, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
8 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), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=a6aa8fca4d792c72947e341d7842d2f700534335 <1ff116f68560a25656933d5a18e7619cb6773d8a || >=a6aa8fca4d792c72947e341d7842d2f700534335 <165b25e3ee9333f7b04f8db43895beacb51582ed || >=a6aa8fca4d792c72947e341d7842d2f700534335 <ae6fc4e6a3322f6d1c8ff59150d8469487a73dd8 || >=a6aa8fca4d792c72947e341d7842d2f700534335 <9d75fab2c14a25553a1664586ed122c316bd1878 || >=a6aa8fca4d792c72947e341d7842d2f700534335 <242b30466879e6defa521573c27e12018276c33a || >=a6aa8fca4d792c72947e341d7842d2f700534335 <a4ee78244445ab73af22bfc5a5fc543963b25aef || >=a6aa8fca4d792c72947e341d7842d2f700534335 <8a283cdfc8beeb14024387a925247b563d614e1e || >=a6aa8fca4d792c72947e341d7842d2f700534335 <b794918961516f667b0c745aebdfebbb8a98df39 || f14ad42b8743897d140808467ed4ae3ce93bd0a5 || >=4.9.68 <4.101ff116f68560a25656933d5a18e7619cb6773d8a, 165b25e3ee9333f7b04f8db43895beacb51582ed, ae6fc4e6a3322f6d1c8ff59150d8469487a73dd8, 9d75fab2c14a25553a1664586ed122c316bd1878, 242b30466879e6defa521573c27e12018276c33a, a4ee78244445ab73af22bfc5a5fc543963b25aef, 8a283cdfc8beeb14024387a925247b563d614e1e, b794918961516f667b0c745aebdfebbb8a98df39, 4.10
Linux/Linuxgeneric4.14Not reported
Siemens/RUGGEDCOM RST2428Pgeneric>=0 <V3.1V3.1
Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric>=0 <V3.1V3.1
Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.0 <V3.1.5V3.1.5
Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric>=V3.1.0 <V3.1.5V3.1.5
Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric>=0 <V1.1.1V1.1.1
Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.0 <V3.1.5V3.1.5

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 1ff116f68560a25656933d5a18e7619cb6773d8a; Siemens/RUGGEDCOM RST2428P to V3.1; Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family to V3.1; Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5; Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5; Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem to V1.1.1; Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 21, 2024

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 15, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Oct 15, 2026

Sources and claim methodology

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

In the Linux kernel, the following vulnerability has been resolved: dma-buf/sw-sync: don't enable IRQ from sync_print_obj() Since commit a6aa8fca4d79 ("dma-buf/sw-sync: Reduce irqsave/irqrestore from known context") by error replaced spin_unlock_irqrestore() with spin_unlock_irq() for both sync_debugfs_show() and sync_print_obj() despite sync_print_obj() is called from sync_debugfs_show(), lockdep complains inconsistent lock state warning. Use plain spin_{lock,unlock}() for sync_print_obj(), for sync_debugfs_show() is already using spin_{lock,unlock}_irq().

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • SODOLA SL902-SWTGW124AS Buffer Overflow DoS via Multipart Boundary ParserSame generic ecosystem
  • Ellucian WebAdvisor 3.2 Unauthenticated XXE InjectionSame generic ecosystem
  • sgl-project SGLang generate Endpoint io_struct.py denial of serviceSame generic ecosystem
  • sgl-project SGLang Session Cleanup session_controller.py Session.create_req denial of serviceSame generic ecosystem
  • ggml-org whisper.cpp Model Loader whisper_model_load out-of-boundsSame generic ecosystem
  • FreeRDP shadow before 3.32.0 Pre-Authentication Input Injection via Confirm Active bypassSame generic ecosystem

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 15, 2026
References
12 linked sources
Open source record