Live › vulnerability › CVE-2026-98577
Go to dashboardThe Linux kernel NFC LLCP code matches service names by prefix, so a short service name such as "u" is treated as a longer well-known service like "urn:nfc:sn:snep". An attacker on a near-field link can likely redirect traffic meant for a standard NFC service to their own service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems with the Linux kernel NFC subsystem and LLCP support built in or loaded, such as devices with NFC hardware. Systems without NFC hardware or with the nfc module not loaded are unlikely to be exposed. unknown for exact affected kernel versions.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap()
nfc_llcp_wks_sap() compares only service_name_len bytes, so a short service_name like "u" matches longer WKS strings like "urn:nfc:sn:snep". Fix by requiring exact length match before strncmp().
This page as .md · .json · in your agent: get_signal("CVE-2026-98577")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.