From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7CE3C1F0E2F for ; Thu, 1 May 2025 14:19:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746109166; cv=none; b=n3OmwXloHzGDM6hbgs8T66O/3myXGa+oJQMQQURiOIRqrSD8DH8c8cyBBbP9t637iiQw16mGye+pcP4l5x8Ir/2vx8KPaL5tnpLe/Uwt6Rfu+58MIbySskcUfPDKFk3CWWXJlsjowQsDSSf7r2Ik4P8q7WGaiyTaCvVvyJUReFc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746109166; c=relaxed/simple; bh=lQp8Ma+Fpti3M+Jf9KKR7c7Q9eaHOIKNu+Nv56Y14ic=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=X59H97l+ujg1y8lsFyNlPk2JkX19ipyfNyw4wTzx2caTROSuex7QwBN+190nAG+UytxyZU93brBKRtBLzXjqzCDR3C036h5hXzrik0BWgIf044FN/7Q3Jm6uzP2YUs80+KUN/Ps/yysVG8sLJ5sl3G5DGKw7OKnrEBSdpBR5uKM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=N9aPJFtu; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="N9aPJFtu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0B1C8C4CEE3; Thu, 1 May 2025 14:19:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1746109166; bh=lQp8Ma+Fpti3M+Jf9KKR7c7Q9eaHOIKNu+Nv56Y14ic=; h=From:To:Cc:Subject:Date:Reply-to:From; b=N9aPJFtumAFHkHnc9aQWKx7NSCBl4PRvRSUtmjsqp6sjximVK3+XM0de0ScAXTaMT zX6sjsSSIM47FymdySGjFTFI4y4rA+nw1x1GC86Fq0qmEION40Smdf2S0w6nuUASyL 6EHVY+Z3JVsb/sQtYBfV0zhS5KcVvYTdiJtm5DUw= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49902: block: Fix possible memory leak for rq_wb on add_disk failure Date: Thu, 1 May 2025 16:11:32 +0200 Message-ID: <2025050102-CVE-2022-49902-59fe@gregkh> X-Mailer: git-send-email 2.49.0 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3181; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=XbReVUNeHB2EtQGI0HN95s+XVI8+E3WR9pmX4gsCE6k=; b=owGbwMvMwCRo6H6F97bub03G02pJDBnCDbtkz0burm/vu/R97sSlsZ8lHS77XuZfzd1+JCXx0 cTA0vWcHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRCa8ZFvT0yB4/KTZL6aSj vFBOc9na5bdCexjmZ7vk6XZxWsQXB7qvCrbqEZ3NLtIOAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: block: Fix possible memory leak for rq_wb on add_disk failure kmemleak reported memory leaks in device_add_disk(): kmemleak: 3 new suspected memory leaks unreferenced object 0xffff88800f420800 (size 512): comm "modprobe", pid 4275, jiffies 4295639067 (age 223.512s) hex dump (first 32 bytes): 04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00 ................ 00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000d3662699>] kmalloc_trace+0x26/0x60 [<00000000edc7aadc>] wbt_init+0x50/0x6f0 [<0000000069601d16>] wbt_enable_default+0x157/0x1c0 [<0000000028fc393f>] blk_register_queue+0x2a4/0x420 [<000000007345a042>] device_add_disk+0x6fd/0xe40 [<0000000060e6aab0>] nbd_dev_add+0x828/0xbf0 [nbd] ... It is because the memory allocated in wbt_enable_default() is not released in device_add_disk() error path. Normally, these memory are freed in: del_gendisk() rq_qos_exit() rqos->ops->exit(rqos); wbt_exit() So rq_qos_exit() is called to free the rq_wb memory for wbt_init(). However in the error path of device_add_disk(), only blk_unregister_queue() is called and make rq_wb memory leaked. Add rq_qos_exit() to the error path to fix it. The Linux kernel CVE team has assigned CVE-2022-49902 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 83cbce9574462c6b4eed6797bdaf18fae6859ab3 and fixed in 5.15.78 with commit 4e68c5da60cd79950bd56287ae80b39d6261f995 Issue introduced in 5.15 with commit 83cbce9574462c6b4eed6797bdaf18fae6859ab3 and fixed in 6.0.8 with commit 528677d3b4af985445bd4ac667485ded1ed11220 Issue introduced in 5.15 with commit 83cbce9574462c6b4eed6797bdaf18fae6859ab3 and fixed in 6.1 with commit fa81cbafbf5764ad5053512152345fab37a1fe18 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2022-49902 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: block/genhd.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/4e68c5da60cd79950bd56287ae80b39d6261f995 https://git.kernel.org/stable/c/528677d3b4af985445bd4ac667485ded1ed11220 https://git.kernel.org/stable/c/fa81cbafbf5764ad5053512152345fab37a1fe18