6 matches found
CVE-2025-40318
CVE-2025-40318 : In the Linux kernel, Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once. The root cause was a race between hci_cmd_sync_dequeue_once() performing a lookup then cancel under one lock section while hci_cmd_sync_work() could also delete the same entry, causing a double list_...
CVE-2022-49995
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdiunregister gets called to stop further writeback and wait for associated delayed work to complete. However, wbinodewritebackend may schedule bandwid...
UBUNTU-CVE-2022-49995
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdiunregister gets called to stop further writeback and wait for associated delayed work to complete. However, wbinodewritebackend may schedule bandwid...
CVE-2022-49995 writeback: avoid use-after-free after removing device
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdiunregister gets called to stop further writeback and wait for associated delayed work to complete. However, wbinodewritebackend may schedule bandwid...
CVE-2022-49995 writeback: avoid use-after-free after removing device
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdiunregister gets called to stop further writeback and wait for associated delayed work to complete. However, wbinodewritebackend may schedule bandwid...
CVE-2022-49995
The connected sources confirm CVE-2022-49995 is a Linux kernel use-after-free in writeback code when removing a disk. Specifically, wb_inode_writeback_end() could schedule work to access a freed bdi_writeback; the fix switches wb->work_lock to an irqsafe lock and checks that bdi_writeback is a...