CVE-2026-98483: Linux Vulnerability

Description

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

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 96f2c6f272ec04083d828de46285a7d7b17d1aad, < 25bfa673adc70189c0bc872940421ae59f789cf6; >= fc8429f8d86801f092fbfbd257c3af821ac0dcd3, < 2b31d0cc95856c856ada91f943fb14dfdf29a923; >= 425d9d3a92df7d96b3cfb7ee5c240293a21cbde3, < c40f61a6a413f3eaf028e5fe367fd9749e503ab0; >= 6709d4b7bc2e079241fdef15d1160581c5261c10, < 19bcfc2a56d0b82919079b5424c5a9a0ac897dcf; >= 6709d4b7bc2e079241fdef15d1160581c5261c10, < d8c929e9afdbc33b1876ecb97a517e850449b5bd; >= 6709d4b7bc2e079241fdef15d1160581c5261c10, < 841af260ff477f6191872bc3b2e15488615c1827; >= 6709d4b7bc2e079241fdef15d1160581c5261c10, < 9ede11e12f965ace97c4e0f606667f24fb41e7e1; >= 6709d4b7bc2e079241fdef15d1160581c5261c10, < dcab71a7011918f6fdba7adcec02d217dcb84b8d; dd6ff3f3862709ab1a12566e73b9d6a9b8f6e548; b3ad46e155a6d91b36c6e892019a43e3ef3c696d; e5207c1d69b1a9707615ab6ff9376e59fc096815; >= 5.10.188, < 5.10.271; >= 5.15.121, < 5.15.222; >= 6.1.39, < 6.1.189; >= 5.4.251, < 5.5; >= 6.3.13, < 6.4; >= 6.4.4, < 6.5
Linux	Linux	6.5

References

Timeline

Published: Oct 18, 2026
Last Modified: Oct 19, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-98483?

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

How severe is CVE-2026-98483?

Severity scoring for CVE-2026-98483 is pending analysis.

How do I fix CVE-2026-98483?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →