Out-of-bounds read via truncated NFC inventory responses
Published Oct 18, 2026 · Updated Oct 18, 2026
Missing length checks in Linux's st21nfca NFC driver allow attackers to trigger out-of-bounds reads via short ISO15693 responses. The st21nfca_get_iso15693_inventory helper strips a two-byte prefix without verifying success, then accepts a one-byte remainder before reading data[1] as the DSFID. Reachability requires the affected NFC inventory path; the disclosure establishes an invalid read, not external data disclosure or code execution.
Summary
What happened
Missing length checks in Linux's st21nfca NFC driver allow attackers to trigger out-of-bounds reads via short ISO15693 responses. The st21nfca_get_iso15693_inventory helper strips a two-byte prefix without verifying success, then accepts a one-byte remainder before reading data[1] as the DSFID. Reachability requires the affected NFC inventory path; the disclosure establishes an invalid read, not external data disclosure or code execution.
The record
- CVE
- CVE-2026-98578
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 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=3.16
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <3af2ea4035581a1607d9830779c187a0c7e225aa
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <57d183764f3002f9625ee4deeeb20716c519534e
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <6353dae51bc9b3cad13c9d890b53311a46c96b4e
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <7f2ea5ed588c03d481f0301e6c3d4240132383fb
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <9fa21b0f78adb514e3bd96a505ddb752e9727ff3
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <a86987d03a4d39acdbe4533d83db4d656ea36c59
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <e47b2a350bb0ff123434ec5484c6dc3333b0727c
- Affected versionversion=7974728094d35f38775417a26d8f30ea3602496a <fdd95e819d828c975aaeb258a3fed5dd7fd136d0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started