From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80803: nfc: digital: clamp SENSF_RES length to the destination buffer
Date: Fri, 4 Sep 2026 17:11:42 +0200 [thread overview]
Message-ID: <2026090409-CVE-2026-80803-7853@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfc: digital: clamp SENSF_RES length to the destination buffer
digital_in_recv_sensf_res() memcpy()s resp->len bytes from a remote
NFC-F device response into the NFC_SENSF_RES_MAXSIZE-byte target.sensf_res
field without an upper-bound check. A nearby malicious NFC-F device can
send an oversized SENSF_RES response to overflow the stack-local struct
nfc_target.
Clamp resp->len to NFC_SENSF_RES_MAXSIZE before the copy.
Found by 0sec automated security-research tooling (https://0sec.ai).
The Linux kernel CVE team has assigned CVE-2026-80803 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 5.10.267 with commit 6afb29751ee731e7f7a96feb8a15f91441e552ba
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 5.15.218 with commit e886c63d2ca7108826076989103a1ffa8a0bb8f4
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 6.1.185 with commit 4e942da2869bcd646353eef706b7dd82efeb9db5
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 6.6.154 with commit d0756a98277e383c26fead988a96c91f0781cd7f
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 6.12.106 with commit af4c0606f743e009254a8d252096855335ade85d
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 6.18.47 with commit a56773e649ea99b344d6bbaf90f34c8e3fadef5d
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 7.1.11 with commit a1ef9bddfbb3ae42b036c5aa16cf386d78db70b6
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 7.2.1 with commit 31aa28ed732f66ab83c40ef53d99791be69b85c4
Issue introduced in 3.13 with commit 8c0695e4998dd268ff2a05951961247b7e015651 and fixed in 7.3-rc1 with commit 344a56d7c8e0f3cbaff0bcb1bcd95a1a1db24b16
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-80803
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/digital_technology.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/6afb29751ee731e7f7a96feb8a15f91441e552ba
https://git.kernel.org/stable/c/e886c63d2ca7108826076989103a1ffa8a0bb8f4
https://git.kernel.org/stable/c/4e942da2869bcd646353eef706b7dd82efeb9db5
https://git.kernel.org/stable/c/d0756a98277e383c26fead988a96c91f0781cd7f
https://git.kernel.org/stable/c/af4c0606f743e009254a8d252096855335ade85d
https://git.kernel.org/stable/c/a56773e649ea99b344d6bbaf90f34c8e3fadef5d
https://git.kernel.org/stable/c/a1ef9bddfbb3ae42b036c5aa16cf386d78db70b6
https://git.kernel.org/stable/c/31aa28ed732f66ab83c40ef53d99791be69b85c4
https://git.kernel.org/stable/c/344a56d7c8e0f3cbaff0bcb1bcd95a1a1db24b16
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-80803-7853@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.