From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43291: net: nfc: nci: Fix parameter validation for packet data
Date: Fri, 8 May 2026 15:11:56 +0200 [thread overview]
Message-ID: <2026050853-CVE-2026-43291-6242@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: nfc: nci: Fix parameter validation for packet data
Since commit 9c328f54741b ("net: nfc: nci: Add parameter validation for
packet data") communication with nci nfc chips is not working any more.
The mentioned commit tries to fix access of uninitialized data, but
failed to understand that in some cases the data packet is of variable
length and can therefore not be compared to the maximum packet length
given by the sizeof(struct).
The Linux kernel CVE team has assigned CVE-2026-43291 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15.195 with commit 8fcc7315a10a84264e55bb65ede10f0af20a983f and fixed in 5.15.202 with commit a24a8a582da4426b2042e510a1080df84083b51d
Issue introduced in 6.1.156 with commit bfdda0123dde406dbff62e7e9136037e97998a15 and fixed in 6.1.165 with commit f5218426f765eee22e178df9c126d974792fb6a5
Issue introduced in 6.6.112 with commit 0ba68bea1e356f466ad29449938bea12f5f3711f and fixed in 6.6.128 with commit ad058a4317db7fdb3f09caa6ed536d24a62ce6a0
Issue introduced in 6.12.53 with commit 74837bca0748763a77f77db47a0bdbe63b347628 and fixed in 6.12.75 with commit 3b91160e9a91b5a2662875417dc42dc5b0bf03ea
Issue introduced in 6.18 with commit 9c328f54741bd5465ca1dc717c84c04242fac2e1 and fixed in 6.18.16 with commit c692db813a7e3b7c3c17d6e9a3ad2a018bf1142b
Issue introduced in 6.18 with commit 9c328f54741bd5465ca1dc717c84c04242fac2e1 and fixed in 6.19.6 with commit 498fc5d0d650c77e87fcc73808d4f43240c21805
Issue introduced in 6.18 with commit 9c328f54741bd5465ca1dc717c84c04242fac2e1 and fixed in 7.0 with commit 571dcbeb8e635182bb825ae758399831805693c2
Issue introduced in 6.17.3 with commit c395d1e548cc68e84584ffa2e3ca9796a78bf7b9
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-2026-43291
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:
net/nfc/nci/ntf.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/a24a8a582da4426b2042e510a1080df84083b51d
https://git.kernel.org/stable/c/f5218426f765eee22e178df9c126d974792fb6a5
https://git.kernel.org/stable/c/ad058a4317db7fdb3f09caa6ed536d24a62ce6a0
https://git.kernel.org/stable/c/3b91160e9a91b5a2662875417dc42dc5b0bf03ea
https://git.kernel.org/stable/c/c692db813a7e3b7c3c17d6e9a3ad2a018bf1142b
https://git.kernel.org/stable/c/498fc5d0d650c77e87fcc73808d4f43240c21805
https://git.kernel.org/stable/c/571dcbeb8e635182bb825ae758399831805693c2
reply other threads:[~2026-05-08 13:13 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=2026050853-CVE-2026-43291-6242@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox