A use-after-free flaw was found in the Linux Kernel. When a disk is removed, bdi_unregister is called to stop further write-back and waits for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation work after this has completed, which can result in the timer attempting to access the recently freed bdi_writeback.
Workaround:
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://access.redhat.com/errata/RHSA-2024:0412 | third party advisory vendor advisory |
| https://access.redhat.com/security/cve/CVE-2024-0562 | third party advisory vdb entry |
| https://bugzilla.redhat.com/show_bug.cgi?id=2258475 | third party advisory issue tracking |
| https://patchwork.kernel.org/project/linux-mm/patch/20220801155034.3772543-1-khazhy@google.com/ | patch mailing list |