NFC communication failure via full-structure length checks
Published May 8, 2026 · Updated May 8, 2026
Improper packet validation in the Linux Kernel allows physically proximate attackers to interrupt communication with NCI NFC chips. The NCI notification handlers in net/nfc/nci/ntf.c compare variable-length packets against full structure sizes and reject valid shorter packets instead of validating each length-bearing field. NFC proximity and an active NCI path are required; rejected discovery, activation, or credit notifications make affected chips unusable.
Summary
What happened
Improper packet validation in the Linux Kernel allows physically proximate attackers to interrupt communication with NCI NFC chips. The NCI notification handlers in net/nfc/nci/ntf.c compare variable-length packets against full structure sizes and reject valid shorter packets instead of validating each length-bearing field. NFC proximity and an active NCI path are required; rejected discovery, activation, or credit notifications make affected chips unusable.
The record
- CVE
- CVE-2026-43291
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-908, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0ba68bea1e356f466ad29449938bea12f5f3711f <ad058a4317db7fdb3f09caa6ed536d24a62ce6a0
- Affected versionversion=6.18
- Affected versionversion=74837bca0748763a77f77db47a0bdbe63b347628 <3b91160e9a91b5a2662875417dc42dc5b0bf03ea
- Affected versionversion=8fcc7315a10a84264e55bb65ede10f0af20a983f <a24a8a582da4426b2042e510a1080df84083b51d
- Affected versionversion=9c328f54741bd5465ca1dc717c84c04242fac2e1 <498fc5d0d650c77e87fcc73808d4f43240c21805
- Affected versionversion=9c328f54741bd5465ca1dc717c84c04242fac2e1 <571dcbeb8e635182bb825ae758399831805693c2
- Affected versionversion=9c328f54741bd5465ca1dc717c84c04242fac2e1 <c692db813a7e3b7c3c17d6e9a3ad2a018bf1142b
- Affected versionversion=bfdda0123dde406dbff62e7e9136037e97998a15 <f5218426f765eee22e178df9c126d974792fb6a5
- Affected versionversion=c395d1e548cc68e84584ffa2e3ca9796a78bf7b9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo