From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80797: nfc: pn533: purge fragmented skbs during cleanup
Date: Fri, 4 Sep 2026 17:11:36 +0200 [thread overview]
Message-ID: <2026090408-CVE-2026-80797-7839@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfc: pn533: purge fragmented skbs during cleanup
pn53x_common_clean() purges resp_q before freeing the common PN533 state,
but it leaves fragment_skb untouched. The fragmentation helpers queue
transmit fragments there while sending large initiator or target-mode
frames, and those skbs remain owned by the driver until they are sent or
discarded.
If the device is removed while fragments are still queued, the common
cleanup path frees the PN533 state without releasing the queued fragment
skbs, leaking them.
Purge fragment_skb during cleanup alongside resp_q.
The Linux kernel CVE team has assigned CVE-2026-80797 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 5.10.267 with commit 130b5ad4492f8e53d0398ee3af2b0e2388504d11
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 5.15.218 with commit 9319c3c4962efc8697246b563ea31c6d47f085aa
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 6.1.185 with commit d63e85c5d5555fe6aa65155d3a09452597e163c3
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 6.6.154 with commit 4a52ec2457ff8c26206fcc20fa1972cc35a678c4
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 6.12.106 with commit e169277281373818ae1cedf976aa1e99118fb77d
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 6.18.47 with commit 2f5d093194ec24d7c29b91bf7df014924e0f4ea1
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 7.1.11 with commit e7ed2ea5590fbe2d3be39ee4fb0c758a12e31d0c
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 7.2.1 with commit e95beff58b38c871c557bf84e528408283c2c0ad
Issue introduced in 3.12 with commit 963a82e07d4e1f95fc423d53912ac0a7fe643b1c and fixed in 7.3-rc1 with commit 5718fc62198c38c2de5316020a90506f9e75e0bb
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-80797
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/pn533/pn533.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/130b5ad4492f8e53d0398ee3af2b0e2388504d11
https://git.kernel.org/stable/c/9319c3c4962efc8697246b563ea31c6d47f085aa
https://git.kernel.org/stable/c/d63e85c5d5555fe6aa65155d3a09452597e163c3
https://git.kernel.org/stable/c/4a52ec2457ff8c26206fcc20fa1972cc35a678c4
https://git.kernel.org/stable/c/e169277281373818ae1cedf976aa1e99118fb77d
https://git.kernel.org/stable/c/2f5d093194ec24d7c29b91bf7df014924e0f4ea1
https://git.kernel.org/stable/c/e7ed2ea5590fbe2d3be39ee4fb0c758a12e31d0c
https://git.kernel.org/stable/c/e95beff58b38c871c557bf84e528408283c2c0ad
https://git.kernel.org/stable/c/5718fc62198c38c2de5316020a90506f9e75e0bb
reply other threads:[~2026-09-04 15:20 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=2026090408-CVE-2026-80797-7839@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.