Kernel crash via uncleared probe-error USB requests
Published Jul 16, 2024 · Updated May 11, 2026
Use-after-free in the Linux kernel NFC port100 driver allows local users to crash the system during a failed USB device probe. On the probe error path, port100_probe omits usb_kill_urb before devres frees device-managed memory, allowing port100_send_complete to access the freed allocation. Triggering the flaw requires local low-privileged access and a compatible NFC USB device or emulation; the published impact is a kernel crash, not data disclosure or modification.
Summary
What happened
Use-after-free in the Linux kernel NFC port100 driver allows local users to crash the system during a failed USB device probe. On the probe error path, port100_probe omits usb_kill_urb before devres frees device-managed memory, allowing port100_send_complete to access the freed allocation. Triggering the flaw requires local low-privileged access and a compatible NFC USB device or emulation; the published impact is a kernel crash, not data disclosure or modification.
The record
- CVE
- CVE-2022-48857
- Published
- Jul 16, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=0347a6ab300a1532c298823408d6e51ccf4e4f45 <0e721b8f2ee5e11376dd55363f9ccb539d754b8a
- Affected versionversion=0347a6ab300a1532c298823408d6e51ccf4e4f45 <205c4ec78e71cbf561794e6043da80e7bae6790f
- Affected versionversion=0347a6ab300a1532c298823408d6e51ccf4e4f45 <2b1c85f56512d49e43bc53741fce2f508cd90029
- Affected versionversion=0347a6ab300a1532c298823408d6e51ccf4e4f45 <32e866ae5a7af590597ef4bcff8451bf96d5f980
- Affected versionversion=0347a6ab300a1532c298823408d6e51ccf4e4f45 <7194737e1be8fdc89d2a9382bd2f371f7ee2eda8
- Affected versionversion=0347a6ab300a1532c298823408d6e51ccf4e4f45 <b1db33d4e54bc35d8db96ce143ea0ef92e23d58e
- Affected versionversion=0347a6ab300a1532c298823408d6e51ccf4e4f45 <cd2a5c0da0d1ddf11d1f84e9c9b1949f50f6e161
- Affected versionversion=0347a6ab300a1532c298823408d6e51ccf4e4f45 <f80cfe2f26581f188429c12bd937eb905ad3ac7b
- Affected versionversion=3.13
What conditions does exploitation require?
What is affected?
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