Kernel crashes via unchecked USB frame lengths
Published Oct 18, 2026 · Updated Oct 18, 2026
Out-of-bounds reads in Linux's PN533 USB driver allow physically proximate attackers to crash the kernel via crafted USB responses. The pn533_acr122_is_rx_frame_valid() function uses the device-supplied ccid.datalen value to index frame->data without checking its upper bound or rejecting the underflow-producing value 1. Exposure requires the affected ACR122 USB driver path; published testing demonstrates sanitizer-detected crashes, not attacker-visible memory disclosure or code execution.
Summary
What happened
Out-of-bounds reads in Linux's PN533 USB driver allow physically proximate attackers to crash the kernel via crafted USB responses. The pn533_acr122_is_rx_frame_valid() function uses the device-supplied ccid.datalen value to index frame->data without checking its upper bound or rejecting the underflow-producing value 1. Exposure requires the affected ACR122 USB driver path; published testing demonstrates sanitizer-detected crashes, not attacker-visible memory disclosure or code execution.
The record
- CVE
- CVE-2026-98575
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- physical
- 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=4.7
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <2450a388367231fb7dd798538f393af227c00c4d
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <72b8b2126e854d6756a1aa4bdc66d7457b832294
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <74b3fbc60907ee97e3af3249091f57351b53a6d6
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <8a0f1bb790d964893db7fc59febda9a534db07b3
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <8db3b1e012a8b25078dfa1efabe3d0cd2916dcba
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <b61732f47316d45f27706db7812950145d3327b5
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <e72cbedc4596e808d22dd2b9fff666ece76f8dd6
- Affected versionversion=9815c7cf22daceabfb919ddcd6f2c80e049c1fbc <ea82b7576793219fa10a8b545f8338998b2a9ce2
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
Public exploit references
- Syzkaller C crash reproducerproof of concept · demonstrated
- Syzkaller syz crash reproducerproof of concept · demonstrated
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