CVE-2024-38780: Linux kernel · dma-buf/sw-sync: don't enable IRQ from sync_print_obj()
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1130.140~18.04.1 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 15:18 UTC
- Patch
- Available – fixed in 5.4.0-1130.140~18.04.1, 5.4.0-1135.142~18.04.1, 5.4.0-1134.143~18.04.1 +71
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6951-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6953-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6979-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6999-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7004-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7008-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and has been released in multiple Linux kernel versions, including those distributed with Ubuntu 18.04 LTS and later. Users should apply the official kernel updates from their distribution vendors and reboot systems to ensure the fix is applied. The Ubuntu advisory USN-6951-1 confirms the availability of fixes and recommends standard system updates and reboots. Due to ABI changes, recompilation and reinstallation of third-party kernel modules may be necessary after updating.
Description
CVE-2024-38780 is a vulnerability in the Linux kernel's dma-buf/sw-sync subsystem related to improper IRQ handling in the sync_print_obj() function. The issue was caused by an incorrect replacement of spin_unlock_irqrestore() with spin_unlock_irq(), leading to inconsistent lock state warnings from lockdep. This flaw has been fixed by using plain spin_lock and spin_unlock in sync_print_obj(), while sync_debugfs_show() continues to use spin_lock_irq and spin_unlock_irq. The vulnerability affects multiple versions of the Linux kernel, particularly those used in Ubuntu 18.04 LTS and related distributions.
References
- ubuntu.com/security/CVE-2024-38780 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-38780 (opens in a new tab)
- git.kernel.org/linus/b794918961516f667b0c745aebdfebbb8a98df39 (opens in a new tab)
- git.kernel.org/stable/c/1ff116f68560a25656933d5a18e7619cb6773d8a (opens in a new tab)
- git.kernel.org/stable/c/165b25e3ee9333f7b04f8db43895beacb51582ed (opens in a new tab)
- git.kernel.org/stable/c/ae6fc4e6a3322f6d1c8ff59150d8469487a73dd8 (opens in a new tab)
- git.kernel.org/stable/c/9d75fab2c14a25553a1664586ed122c316bd1878 (opens in a new tab)
- git.kernel.org/stable/c/242b30466879e6defa521573c27e12018276c33a (opens in a new tab)
- git.kernel.org/stable/c/a4ee78244445ab73af22bfc5a5fc543963b25aef (opens in a new tab)
- git.kernel.org/stable/c/8a283cdfc8beeb14024387a925247b563d614e1e (opens in a new tab)
- git.kernel.org/stable/c/b794918961516f667b0c745aebdfebbb8a98df39 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6953-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6951-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6979-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6999-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7004-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-1 (opens in a new tab)