[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061809-CVE-2022-49949-8fb5@gregkh>
Date: Wed, 18 Jun 2025 13:00:14 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49949: firmware_loader: Fix memory leak in firmware upload
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
firmware_loader: Fix memory leak in firmware upload
In the case of firmware-upload, an instance of struct fw_upload is
allocated in firmware_upload_register(). This data needs to be freed
in fw_dev_release(). Create a new fw_upload_free() function in
sysfs_upload.c to handle the firmware-upload specific memory frees
and incorporate the missing kfree call for the fw_upload structure.
The Linux kernel CVE team has assigned CVE-2022-49949 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.19 with commit 97730bbb242cde22b7140acd202ffd88823886c9 and fixed in 5.19.8 with commit baf92485d111be828e1ab84a995515b604b938e5
Issue introduced in 5.19 with commit 97730bbb242cde22b7140acd202ffd88823886c9 and fixed in 6.0 with commit 789bba82f63c3e81dce426ba457fc7905b30ac6e
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-49949
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:
drivers/base/firmware_loader/sysfs.c
drivers/base/firmware_loader/sysfs.h
drivers/base/firmware_loader/sysfs_upload.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/baf92485d111be828e1ab84a995515b604b938e5
https://git.kernel.org/stable/c/789bba82f63c3e81dce426ba457fc7905b30ac6e
Powered by blists - more mailing lists