CVE-2022-49901: blk-mq: Fix kmemleak in blk_mq_init_allocated_queue
blk-mq: Fix kmemleak in blkmqinitallocatedqueue
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Apply the fix described: ensure blk_release_queue() is called in the exception path so the hctxs moved to q->unused_hctx_list are released (kmemleak in blk_mq_init_allocated_queue / triggered by modprobe null_blk.ko).
Event History
Frequently Asked Questions
What is the severity of CVE-2022-49901?
CVE-2022-49901 has been classified with a medium severity due to the potential for kernel memory leaks.
How do I fix CVE-2022-49901?
To mitigate CVE-2022-49901, update your Linux kernel to the latest stable version that includes the fix.
What types of systems are affected by CVE-2022-49901?
CVE-2022-49901 affects systems running vulnerable versions of the Linux kernel that utilize the blk-mq IO scheduler.
What is the nature of the vulnerability in CVE-2022-49901?
CVE-2022-49901 involves a memory leak associated with the initialization of a block queue leading to unreferenced memory objects.
Is CVE-2022-49901 related to modprobe or any specific module?
Yes, CVE-2022-49901 is triggered during the loading of the null_blk module via modprobe.