PT-2025-18618 · Linux+3 · Linux Kernel+3
Published
2022-10-31
·
Updated
2026-04-20
·
CVE-2022-49901
CVSS v3.1
5.5
Medium
| Vector | AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Name of the Vulnerable Software and Affected Versions
Linux kernel (affected versions not specified)
Description
A memory leak issue has been identified in the Linux kernel, specifically in the blk-mq module. The leak occurs when the
blk mq init allocated queue function is called, and the q->ma ops is set to NULL before blk release queue is called. This results in a kmemleak, causing unreferenced objects to remain in memory. The issue is caused by the failure of blk mq alloc and init hctx when i is not equal to 0, leading to the allocation of hctxs that are not properly cleaned up. The estimated number of potentially affected devices worldwide is not available.Technical details about exploitation include:
- The
blk mq init allocated queuefunction is vulnerable. - The
q->ma opsvariable is set to NULL beforeblk release queueis called. - The
blk mq alloc and init hctxfunction fails wheniis not equal to 0. - The hctxs allocated by
blk mq alloc and init hctxare moved toq->unused hctx listand are not properly cleaned up.
Recommendations
To resolve the issue, call
blk release queue in the exception path. This will ensure that the hctxs in q->unused hctx list are properly cleaned up, preventing the memory leak. As a temporary workaround, consider disabling the blk mq init allocated queue function until a patch is available. Restrict access to the vulnerable blk-mq module to minimize the risk of exploitation. Avoid using the q->ma ops variable in the affected code path until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.Exploit
Memory Leak
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Astra Linux
Debian
Linux Kernel
Suse