From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2022-49924: nfc: fdp: Fix potential memory leak in fdp_nci_send()
Date: Thu, 1 May 2025 16:11:54 +0200 [thread overview]
Message-ID: <2025050109-CVE-2022-49924-e8b9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfc: fdp: Fix potential memory leak in fdp_nci_send()
fdp_nci_send() will call fdp_nci_i2c_write that will not free skb in
the function. As a result, when fdp_nci_i2c_write() finished, the skb
will memleak. fdp_nci_send() should free skb after fdp_nci_i2c_write()
finished.
The Linux kernel CVE team has assigned CVE-2022-49924 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.4 with commit a06347c04c13e380afce0c9816df51f00b83faf1 and fixed in 5.10.154 with commit e8c11ee2d07f7c4dfa2ac0ea8efc4f627e58ea57
Issue introduced in 4.4 with commit a06347c04c13e380afce0c9816df51f00b83faf1 and fixed in 5.15.78 with commit 44bc1868a4f542502ea2221fe5ad88ca66d1c6b6
Issue introduced in 4.4 with commit a06347c04c13e380afce0c9816df51f00b83faf1 and fixed in 6.0.8 with commit 1a7a898f8f7b56c0eaa2baf67a0c96235a30bc29
Issue introduced in 4.4 with commit a06347c04c13e380afce0c9816df51f00b83faf1 and fixed in 6.1 with commit 8e4aae6b8ca76afb1fb64dcb24be44ba814e7f8a
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-49924
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/nfc/fdp/fdp.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/e8c11ee2d07f7c4dfa2ac0ea8efc4f627e58ea57
https://git.kernel.org/stable/c/44bc1868a4f542502ea2221fe5ad88ca66d1c6b6
https://git.kernel.org/stable/c/1a7a898f8f7b56c0eaa2baf67a0c96235a30bc29
https://git.kernel.org/stable/c/8e4aae6b8ca76afb1fb64dcb24be44ba814e7f8a
reply other threads:[~2025-05-01 14:19 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=2025050109-CVE-2022-49924-e8b9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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.