dma-buf/sw-sync: don't enable IRQ from sync_print_obj()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a6aa8fca4d792c72947e341d7842d2f700534335 · < a4ee78244445ab73af22bfc5a5fc543963b25aef| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel's dma-buf/sw-sync code incorrectly enables interrupts in sync_print_obj(). When sync_debugfs_show() calls it, the mistake can trigger an inconsistent lock-state warning. The input does not specify whether authentication, local access, or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.