Not yet scoredPublished Oct 18, 2026

CVE-2026-98483nfc: fix use-after-free in nfc_get_local_general_bytes

Updated under an hour ago (Oct 28, 2026, 12:23 AM ET)

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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().

CVSS: Not yet scored
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Received
Record last updated: Oct 19, 2026
First seen by InfoSec Signals: Oct 18, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	96f2c6f272ec04083d828de46285a7d7b17d1aad builds before 25bfa673adc70189c0bc872940421ae59f789cf6; from fc8429f8d86801f092fbfbd257c3af821ac0dcd3 before 2b31d0cc95856c856ada91f943fb14dfdf29a923; from 425d9d3a92df7d96b3cfb7ee5c240293a21cbde3 before c40f61a6a413f3eaf028e5fe367fd9749e503ab0; 6709d4b7bc2e079241fdef15d1160581c5261c10 builds before 19bcfc2a56d0b82919079b5424c5a9a0ac897dcf; from 6709d4b7bc2e079241fdef15d1160581c5261c10 before d8c929e9afdbc33b1876ecb97a517e850449b5bd; 6709d4b7bc2e079241fdef15d1160581c5261c10 builds before 841af260ff477f6191872bc3b2e15488615c1827; 6709d4b7bc2e079241fdef15d1160581c5261c10 builds before 9ede11e12f965ace97c4e0f606667f24fb41e7e1; from 6709d4b7bc2e079241fdef15d1160581c5261c10 before dcab71a7011918f6fdba7adcec02d217dcb84b8d; and 9 more ranges	CNA record

References

References

https://git.kernel.org/stable/c/25bfa673adc70189c0bc872940421ae59f789cf6
https://git.kernel.org/stable/c/2b31d0cc95856c856ada91f943fb14dfdf29a923
https://git.kernel.org/stable/c/c40f61a6a413f3eaf028e5fe367fd9749e503ab0
https://git.kernel.org/stable/c/19bcfc2a56d0b82919079b5424c5a9a0ac897dcf
https://git.kernel.org/stable/c/d8c929e9afdbc33b1876ecb97a517e850449b5bd
https://git.kernel.org/stable/c/841af260ff477f6191872bc3b2e15488615c1827
https://git.kernel.org/stable/c/9ede11e12f965ace97c4e0f606667f24fb41e7e1
https://git.kernel.org/stable/c/dcab71a7011918f6fdba7adcec02d217dcb84b8d

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.