From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49422: dmaengine: idxd: Fix the error handling path in idxd_cdev_register()
Date: Wed, 26 Feb 2025 03:11:36 +0100 [thread overview]
Message-ID: <2025022654-CVE-2022-49422-b047@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: Fix the error handling path in idxd_cdev_register()
If a call to alloc_chrdev_region() fails, the already allocated resources
are leaking.
Add the needed error handling path to fix the leak.
The Linux kernel CVE team has assigned CVE-2022-49422 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit 42d279f9137ab7d5503836baec2739284b278d8f and fixed in 5.10.121 with commit 6073af78156b8c3fc1198f8bcc190b7ac3ac0143
Issue introduced in 5.6 with commit 42d279f9137ab7d5503836baec2739284b278d8f and fixed in 5.15.46 with commit b3c7b5d08e9d5b2ff31c03078c00ecf11042419f
Issue introduced in 5.6 with commit 42d279f9137ab7d5503836baec2739284b278d8f and fixed in 5.17.14 with commit 5e88561eceb34ae3f88451c2b8e30fe403484189
Issue introduced in 5.6 with commit 42d279f9137ab7d5503836baec2739284b278d8f and fixed in 5.18.3 with commit c308a2e711a52a47f4b45e7add2b5200169e429a
Issue introduced in 5.6 with commit 42d279f9137ab7d5503836baec2739284b278d8f and fixed in 5.19 with commit aab08c1aac01097815fbcf10fce7021d2396a31f
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-49422
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/dma/idxd/cdev.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/6073af78156b8c3fc1198f8bcc190b7ac3ac0143
https://git.kernel.org/stable/c/b3c7b5d08e9d5b2ff31c03078c00ecf11042419f
https://git.kernel.org/stable/c/5e88561eceb34ae3f88451c2b8e30fe403484189
https://git.kernel.org/stable/c/c308a2e711a52a47f4b45e7add2b5200169e429a
https://git.kernel.org/stable/c/aab08c1aac01097815fbcf10fce7021d2396a31f
reply other threads:[~2025-02-26 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022654-CVE-2022-49422-b047@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.