From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64011: nfc: llcp: Fix use-after-free in llcp_sock_release()
Date: Sun, 19 Jul 2026 16:57:51 +0200 [thread overview]
Message-ID: <2026071909-CVE-2026-64011-41cb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfc: llcp: Fix use-after-free in llcp_sock_release()
llcp_sock_release() unconditionally unlinks the socket from the local
sockets list. However, if the socket is still in connecting state, it
is on the connecting list.
Fix this by checking the socket state and unlinking from the correct list.
The Linux kernel CVE team has assigned CVE-2026-64011 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 5.10.259 with commit 89ba026747019ee643d29407435ddc118e6ca908
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 5.15.210 with commit fb29f6bbe433f3decad227588809636c25f2a287
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 6.1.176 with commit 2dfdaaf7d933b676124aadec6698825e95f94fe9
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 6.6.143 with commit e00f50f8697724a6f1d2d35744c1332c9912dac5
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 6.12.93 with commit cdc17e09a636c7f936f771902535a7515a7608fc
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 6.18.35 with commit 912ebc49d4406a17fe73e5671d674fbc2f6b2634
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 7.0.12 with commit bc421d0826dedbba37580a25405eafb599e76d42
Issue introduced in 3.11 with commit b4011239a08e7e6c2c6e970dfa9e8ecb73139261 and fixed in 7.1 with commit f4268b466190dae95a7585f69b4f1f8ad097632c
Issue introduced in 3.10.10 with commit da989ee1c7702050741a551df6866cc1588f277b
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-64011
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/llcp_sock.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/89ba026747019ee643d29407435ddc118e6ca908
https://git.kernel.org/stable/c/fb29f6bbe433f3decad227588809636c25f2a287
https://git.kernel.org/stable/c/2dfdaaf7d933b676124aadec6698825e95f94fe9
https://git.kernel.org/stable/c/e00f50f8697724a6f1d2d35744c1332c9912dac5
https://git.kernel.org/stable/c/cdc17e09a636c7f936f771902535a7515a7608fc
https://git.kernel.org/stable/c/912ebc49d4406a17fe73e5671d674fbc2f6b2634
https://git.kernel.org/stable/c/bc421d0826dedbba37580a25405eafb599e76d42
https://git.kernel.org/stable/c/f4268b466190dae95a7585f69b4f1f8ad097632c
reply other threads:[~2026-07-19 15:03 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=2026071909-CVE-2026-64011-41cb@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