LiveActive security incident?Get immediate response
CVE Record

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

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().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in dma-buf sw-sync debug handling. A prior change used the wrong spinlock unlock variant, which could re-enable interrupts in a nested debug path and trigger lockdep warnings. The public record does not provide CVSS, impact severity, or evidence of active exploitation.

Executive priority

Treat this as a kernel maintenance item, not an emergency based on available evidence. Track it through normal vulnerability management, with higher urgency for managed appliances or embedded systems where vendor advisories confirm exposure.

Technical view

sync_print_obj() is called from sync_debugfs_show(), which already uses IRQ-aware spin locking. The vulnerable change replaced spin_unlock_irqrestore() with spin_unlock_irq() in both paths. The fix uses plain spin_lock()/spin_unlock() inside sync_print_obj() to avoid inconsistent IRQ state handling.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds containing the referenced dma-buf/sw-sync change before the stable fixes. Downstream advisories from Debian LTS and Siemens indicate some packaged or embedded products track this issue, but product-specific impact must be confirmed with vendor advisories.

Exploitation context

The source bundle shows no KEV listing, no cited active exploitation, no exploit details, and no CVSS score. The described symptom is a lockdep inconsistent lock state warning, but the public record does not establish practical attacker impact.

Researcher notes

The key issue is IRQ state handling across nested dma-buf sw-sync debug functions. Evidence is strongest for the code-level fix, but weak for real-world security impact. Avoid extrapolating privilege escalation, denial of service, or exploitability without additional vendor or kernel maintainer evidence.

Mitigation direction

  • Check distribution or appliance vendor advisories for fixed kernel packages.
  • Update affected Linux kernels to vendor-supported releases containing the stable fix.
  • For Siemens products, follow the relevant Siemens ProductCERT advisory guidance.
  • Prioritize internet-exposed or safety-critical Linux appliances for vendor confirmation.
  • Do not rely on unverified local workarounds absent vendor guidance.

Validation and detection

  • Inventory Linux kernel versions and vendor firmware using affected products.
  • Confirm whether the fixed stable commit is present in each deployed kernel.
  • Review Debian LTS and Siemens advisories for matching product/version statements.
  • Check kernel maintenance channels for backported fixes in custom builds.
  • Document any systems awaiting vendor confirmation or kernel updates.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-38780 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
13Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa6aa8fca4d792c72947e341d7842d2f700534335, a6aa8fca4d792c72947e341d7842d2f700534335, a6aa8fca4d792c72947e341d7842d2f700534335, a6aa8fca4d792c72947e341d7842d2f700534335, a6aa8fca4d792c72947e341d7842d2f700534335, a6aa8fca4d792c72947e341d7842d2f700534335, a6aa8fca4d792c72947e341d7842d2f700534335, a6aa8fca4d792c72947e341d7842d2f700534335, f14ad42b8743897d140808467ed4ae3ce93bd0a5unaffected
LinuxLinux4.14, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.4, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.