CVE-2026-23150 json
nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame().
published 2026-02-14 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-5886
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame().
syzbot reported various memory leaks related to NFC, struct nfc_llcp_sock, sk_buff, nfc_dev, etc. [0]
The leading log hinted that nfc_llcp_send_ui_frame() failed to allocate skb due to sock_error(sk) being -ENXIO.
ENXIO is set by nfc_llcp_socket_release() when struct nfc_llcp_local is destroyed by local_cleanup().
The problem is that there is no synchronisation between nfc_llcp_send_ui_frame() and local_cleanup(), and skb could be put into local->tx_queue after it was purged in local_cleanup():
CPU1 CPU2 ---- ---- nfc_llcp_send_ui_frame() local_cleanup() |- do { ' |- pdu = nfc_alloc_send_skb(..., &err) | . | |- nfc_llcp_socket_release(local, false, ENXIO); | |- skb_queue_purge(&local->tx_queue); | | ' | |- skb_queue_tail(&local->tx_queue, pdu); | ... | |- pdu = nfc_alloc_send_skb(..., &err) | ^._________________________________.'
local_cleanup() is called for struct nfc_llcp_local only after nfc_llcp_remove_local() unlinks it from llcp_devices.
If we hold local->tx_queue.lock then, we can synchronise the thread and nfc_llcp_send_ui_frame().
Let's do that and check list_empty(&local->list) before queuing skb to local->tx_queue in nfc_llcp_send_ui_frame().
[0]: [ 56.074943][ T6096] llcp: nfc_llcp_send_ui_frame: Could not allocate PDU (error=-6) [ 64.318868][ T5813] kmemleak: 6 new suspected memory leaks (see /sys/kernel/debug/kmemleak) BUG: memory leak unreferenced object 0xffff8881272f6800 (size 1024): comm "syz.0.17", pid 6096, jiffies 4294942766 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 27 00 03 40 00 00 00 00 00 00 00 00 00 00 00 00 '..@............ backtrace (crc da58d84d): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4979 [inline] slab_alloc_node mm/slub.c:5284 [inline] __do_kmalloc_node mm/slub.c:5645 [inline] __kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5658 kmalloc_noprof include/linux/slab.h:961 [inline] sk_prot_alloc+0x11a/0x1b0 net/core/sock.c:2239 sk_alloc+0x36/0x360 net/core/sock.c:2295 nfc_llcp_sock_alloc+0x37/0x130 net/nfc/llcp_sock.c:979 llcp_sock_create+0x71/0xd0 net/nfc/llcp_sock.c:1044 nfc_sock_create+0xc9/0xf0 net/nfc/af_nfc.c:31 __sock_create+0x1a9/0x340 net/socket.c:1605 sock_create net/socket.c:1663 [inline] __sys_socket_create net/socket.c:1700 [inline] __sys_socket+0xb9/0x1a0 net/socket.c:1747 __do_sys_socket net/socket.c:1761 [inline] __se_sys_socket net/socket.c:1759 [inline] __x64_sys_socket+0x1b/0x30 net/socket.c:1759 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f
BUG: memory leak unreferenced object 0xffff88810fbd9800 (size 240): comm "syz.0.17", pid 6096, jiffies 4294942850 hex dump (first 32 bytes): 68 f0 ff 08 81 88 ff ff 68 f0 ff 08 81 88 ff ff h.......h....... 00 00 00 00 00 00 00 00 00 68 2f 27 81 88 ff ff .........h/'.... backtrace (crc 6cc652b1): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4979 [inline] slab_alloc_node mm/slub.c:5284 [inline] kmem_cache_alloc_node_noprof+0x36f/0x5e0 mm/slub.c:5336 __alloc_skb+0x203/0x240 net/core/skbuff.c:660 alloc_skb include/linux/skbuff.h:1383 [inline] alloc_skb_with_frags+0x69/0x3f0 net/core/sk ---truncated---
Patch / fix
- Linux Linux 5.10.249, 5.15.199, 6.1.162, 6.6.123, 6.12.69, 6.18.9, 6.19
- linux Debian 12 6.1.162-1
- linux Debian 13 6.12.69-1
- linux Debian 14 6.18.9-1
debian advisories DEBIAN-CVE-2026-23150
- linux Ubuntu 22.04 LTS 5.15.0-176.186
- linux Ubuntu 24.04 LTS 6.8.0-117.117
- linux-aws Ubuntu 22.04 LTS 5.15.0-1105.112
- linux-aws Ubuntu 24.04 LTS 6.8.0-1055.58
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1105.114
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1058.61
- linux-gke Ubuntu 22.04 LTS 5.15.0-1101.107
- linux-gke Ubuntu 24.04 LTS 6.8.0-1054.60
ubuntu advisories UBUNTU-CVE-2026-23150
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.34.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.34.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.34.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-obs-build SLE Module for Development Tools 15 SP7 6.4.0-150700.53.34.1
- kernel-default-base SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1.150700.17.23.1
suse advisories SUSE-SU-2026:1081-1SUSE-SU-2026:20873-1SUSE-SU-2026:20838-1SUSE-SU-2026:20931-1SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.27.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.27.1
opensuse advisories openSUSE-SU-2026:20416-1
- git.kernel.org/stable/c/ab660cb8e17aa93426d1e821c2cce60e4b9bc56a commit
- git.kernel.org/stable/c/65e976e1f474ae3bf5681d7abafb8f3fdb34b8cc commit
- git.kernel.org/stable/c/6734ff1ac6beba1d0c22dc9a3dc1849b773b511f commit
- git.kernel.org/stable/c/f8d002626d434f5fea9085e2557711c16a15cec6 commit
- git.kernel.org/stable/c/3098e5c8af0f4c8f7eebbb370798df8aa2e12ba5 commit
- git.kernel.org/stable/c/61858cbce6ca4bef9ed116c689a4be9520841339 commit
- git.kernel.org/stable/c/165c34fb6068ff153e3fc99a932a80a9d5755709 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-23150 updated
kernel: nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/ab660cb8e17aa93426d1e821c2cce60e4b9bc56a
patch
-
git.kernel.org
/stable/c/65e976e1f474ae3bf5681d7abafb8f3fdb34b8cc
patch
-
git.kernel.org
/stable/c/6734ff1ac6beba1d0c22dc9a3dc1849b773b511f
patch
-
git.kernel.org
/stable/c/f8d002626d434f5fea9085e2557711c16a15cec6
patch
-
git.kernel.org
/stable/c/3098e5c8af0f4c8f7eebbb370798df8aa2e12ba5
patch
-
git.kernel.org
/stable/c/61858cbce6ca4bef9ed116c689a4be9520841339
patch
-
git.kernel.org
/stable/c/165c34fb6068ff153e3fc99a932a80a9d5755709
patch
Sources
- CVE List CVE-2026-23150
- NVD CVE-2026-23150
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.