nfc: fix use-after-free in nfc_get_local_general_bytes
CVE-2026-98483 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-98483, released October 19, 2026. It is not reported as exploited. Patch Radar priority: High.
In the Linux kernel, the following vulnerability has been resolved: nfc: fix use-after-free in nfc_get_local_general_bytes Commit 6709d4b7bc2e ("net: nfc: Fix use-after-free caused by nfc_llcp_find_local") attempted to fix a use-after-free (UAF) issue by invoking nfc_llcp_local_put(local) after accessing local->gb. However, if the reference count drops to zero, local is freed immediately, leading to a use-after-free when callers access the returned pointer. Alternative approaches using dynamic allocation (e.g. kmemdup) introduced memory leaks because callers consistently treat the returned pointer as borrowed memory. Fix this properly by refactoring nfc_llcp_general_bytes() and nfc_get_local_general_bytes() to accept a caller-provided output buffer (out_gb) and its maximum length (gb_max_len). The general bytes are safely copied into out_gb before calling nfc_llcp_local_put(local), ensuring safe lifetime management without ownership transfer complications. Update all callers across drivers (microread, pn533, pn544, st21nfca, digital_dep, and nci) to provide their own destination buffers and pass them to nfc_get_local_general_bytes().
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| linux · Debian 12.15 (bookworm) | 6.1.190-1 | DEBIAN-CVE-2026-98483 | Oct 19, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.113-1 | DEBIAN-CVE-2026-98483 | Oct 19, 2026 |
| linux · Debian 14 | 7.2.9-1 | DEBIAN-CVE-2026-98483 | Oct 19, 2026 |
| linux-6.12 · Debian 12.15 (bookworm) | 6.12.113-1~deb12u1 | DEBIAN-CVE-2026-98483 | Oct 19, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.