Driver probe failure via mismatched USB endpoint
Published Dec 30, 2025 · Updated Dec 30, 2025
Endpoint validation in affected Linux kernels allows physically proximate attackers to trigger an udlfb driver probe failure via USB. The dlfb_usb_probe function accepts any bulk-OUT endpoint, while dlfb_submit_urb always sends through endpoint 1 without verifying that endpoint 1 is bulk-OUT. Exploitation requires attachment or emulation of a crafted USB DisplayLink device; the observed result is a kernel warning and rejected driver probe, not a system crash.
Summary
What happened
Endpoint validation in affected Linux kernels allows physically proximate attackers to trigger an udlfb driver probe failure via USB. The dlfb_usb_probe function accepts any bulk-OUT endpoint, while dlfb_submit_urb always sends through endpoint 1 without verifying that endpoint 1 is bulk-OUT. Exploitation requires attachment or emulation of a crafted USB DisplayLink device; the observed result is a kernel warning and rejected driver probe, not a system crash.
The record
- CVE
- CVE-2023-54277
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record 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=4df1584738f1dc6f0dd854d258bba48591f1ed0e <9e12c58a5ece41be72157cef348576b135c9fc72
- Affected versionversion=5.18
- Affected versionversion=895ea8a290ba87850bcaf2ecfcddef75a014fa54
- Affected versionversion=aaf7dbe07385e0b8deb7237eca2a79926bbc7091 <c8fdf7feca77cd99e25ef0a1e9e72dfc83add8ef
- Affected versionversion=aaf7dbe07385e0b8deb7237eca2a79926bbc7091 <e19383e5dee5adbf3d19f3f210f440a88d1b7dde
- Affected versionversion=aaf7dbe07385e0b8deb7237eca2a79926bbc7091 <ed9de4ed39875706607fb08118a58344ae6c5f42
- Affected versionversion=c4fb41bdf4d6ccca850c4af5d707d14a0fb717a7 <58ecc165abdaed85447455e6dc396758e8c6f219
- Affected versionversion=f6db63819db632158647d5bbf4d7d2d90dc1a268 <1522dc58bff87af79461b96d90ec122e9e726004
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.
Weakness, pattern, technique
Public exploit references
- syzbot USB descriptor 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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo