From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80801: nfc: microread: validate target discovery payload lengths
Date: Fri, 4 Sep 2026 17:11:40 +0200 [thread overview]
Message-ID: <2026090409-CVE-2026-80801-fb51@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfc: microread: validate target discovery payload lengths
microread_target_discovered() parses target discovery payloads from
skb->data according to the HCI gate. The fixed field offsets and UID
copies were checked only against the destination nfc_target buffers, not
against the actual skb length.
Validate that each gate-specific payload contains the fixed fields and
UID bytes before reading or copying them.
The Linux kernel CVE team has assigned CVE-2026-80801 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 5.10.267 with commit c6de4241f2efbbab286efbb84a9c7190298b3052
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 5.15.218 with commit 92a6f0201bb68391b5eba1b3f330af007d7323b6
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 6.1.185 with commit cb298672282421159e53ab311fe49d204c8a52da
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 6.6.154 with commit 18f02354ed229b8e4561b580812d026e7eb29c85
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 6.12.106 with commit e6397fe7b8b5ef18e051f49612d40ff476c5f7d9
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 6.18.47 with commit d0902a7c454326c6384c614226ab8987f3fd425d
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 7.1.11 with commit dabfa26a208e56f4d8dbf26fddc48f188bdb0649
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 7.2.1 with commit 953963b9ac5eecbb316617d337bfaa3d731e3c5e
Issue introduced in 3.9 with commit cfad1ba87150e198be9ea32367a24e500e59de2c and fixed in 7.3-rc1 with commit 25519469972ef57c3edb1805dabd6c5612b90211
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-80801
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/microread/microread.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/c6de4241f2efbbab286efbb84a9c7190298b3052
https://git.kernel.org/stable/c/92a6f0201bb68391b5eba1b3f330af007d7323b6
https://git.kernel.org/stable/c/cb298672282421159e53ab311fe49d204c8a52da
https://git.kernel.org/stable/c/18f02354ed229b8e4561b580812d026e7eb29c85
https://git.kernel.org/stable/c/e6397fe7b8b5ef18e051f49612d40ff476c5f7d9
https://git.kernel.org/stable/c/d0902a7c454326c6384c614226ab8987f3fd425d
https://git.kernel.org/stable/c/dabfa26a208e56f4d8dbf26fddc48f188bdb0649
https://git.kernel.org/stable/c/953963b9ac5eecbb316617d337bfaa3d731e3c5e
https://git.kernel.org/stable/c/25519469972ef57c3edb1805dabd6c5612b90211
reply other threads:[~2026-09-04 15:17 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=2026090409-CVE-2026-80801-fb51@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.