Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-38780, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 92% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < 1ff116f68560a25656933d5a18e7619cb6773d8a
    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < 165b25e3ee9333f7b04f8db43895beacb51582ed
    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < ae6fc4e6a3322f6d1c8ff59150d8469487a73dd8
    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < 9d75fab2c14a25553a1664586ed122c316bd1878
    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < 242b30466879e6defa521573c27e12018276c33a
    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < a4ee78244445ab73af22bfc5a5fc543963b25aef
    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < 8a283cdfc8beeb14024387a925247b563d614e1e
    • affected a6aa8fca4d792c72947e341d7842d2f700534335 – < b794918961516f667b0c745aebdfebbb8a98df39
    • affected f14ad42b8743897d140808467ed4ae3ce93bd0a5
    • affected 4.9.68 – < 4.10
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 4.19.316 – ≤ 4.19.*
    • unaffected 5.4.278 – ≤ 5.4.*
    • unaffected 5.10.219 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.9.4 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References12

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-38780 badge
[![CVE-2024-38780](https://cveledger.app/badge/CVE-2024-38780.svg)](https://cveledger.app/cve/CVE-2024-38780)

Record last updated .