Lucene search

K
nvd416baaa9-dc9f-4396-8d5f-8c081fb06d67NVD:CVE-2024-38780
HistoryJun 21, 2024 - 12:15 p.m.

CVE-2024-38780

2024-06-2112:15:11
CWE-667
416baaa9-dc9f-4396-8d5f-8c081fb06d67
web.nvd.nist.gov
3
linux kernel
vulnerability
dma-buf/sw-sync
resolved

5.5 Medium

CVSS3

Attack Vector

LOCAL

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

NONE

Availability Impact

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

0.0004 Low

EPSS

Percentile

5.1%

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 configurations

NVD
Node
linuxlinux_kernelRange<4.14
OR
linuxlinux_kernelRange4.194.19.316
OR
linuxlinux_kernelRange5.45.4.278
OR
linuxlinux_kernelRange5.105.10.219
OR
linuxlinux_kernelRange5.155.15.161
OR
linuxlinux_kernelRange6.16.1.93
OR
linuxlinux_kernelRange6.66.6.33
OR
linuxlinux_kernelRange6.96.9.4
OR
linuxlinux_kernelMatch6.10.0rc1

5.5 Medium

CVSS3

Attack Vector

LOCAL

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

NONE

Availability Impact

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

0.0004 Low

EPSS

Percentile

5.1%