CVE-2024-38780

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

MEDIUM
5.5
CVSS Score
Published: June 21, 2024 at 11:15 AM UTC
Updated: October 15, 2026 at 01:18 AM UTC
10 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.144.19 ≤ v < 4.19.3165.10 ≤ v < 5.10.2195.15 ≤ v < 5.15.1615.4 ≤ v < 5.4.2786.1 ≤ v < 6.1.936.6 ≤ v < 6.6.336.9 ≤ v < 6.9.44.9.686.10.06.10.0 rc1a6aa8fca4d792c72947e341d7842d2f700534335f14ad42b8743897d140808467ed4ae3ce93bd0a5
Vendor states this is fixed in 165b25e3ee9333f7b04f8db43895beacb51582ed (fixed)
Vendor states this is fixed in 1ff116f68560a25656933d5a18e7619cb6773d8a (fixed)
Vendor states this is fixed in 242b30466879e6defa521573c27e12018276c33a (fixed)
Vendor states this is fixed in 8a283cdfc8beeb14024387a925247b563d614e1e (fixed)
Vendor states this is fixed in 9d75fab2c14a25553a1664586ed122c316bd1878 (fixed)
Vendor states this is fixed in a4ee78244445ab73af22bfc5a5fc543963b25aef (fixed)
Vendor states this is fixed in ae6fc4e6a3322f6d1c8ff59150d8469487a73dd8 (fixed)
Vendor states this is fixed in b794918961516f667b0c745aebdfebbb8a98df39 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.14 (unaffected)
Vendor states this is fixed in 4.19.316 (unaffected)
Vendor states this is fixed in 5.10.219 (unaffected)
Vendor states this is fixed in 5.15.161 (unaffected)
Vendor states this is fixed in 5.4.278 (unaffected)
Vendor states this is fixed in 6.1.93 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.6.33 (unaffected)
Vendor states this is fixed in 6.9.4 (unaffected)
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement

References (12)

Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/165b25e3ee9333f7b04f8db43895beacb51582ed
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1ff116f68560a25656933d5a18e7619cb6773d8a
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/242b30466879e6defa521573c27e12018276c33a
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8a283cdfc8beeb14024387a925247b563d614e1e
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9d75fab2c14a25553a1664586ed122c316bd1878
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a4ee78244445ab73af22bfc5a5fc543963b25aef
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ae6fc4e6a3322f6d1c8ff59150d8469487a73dd8
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b794918961516f667b0c745aebdfebbb8a98df39

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card