Pre-handshake service crash via leaked packet allocations
Published Aug 1, 2025 · Updated Aug 20, 2025
Memory exhaustion in LiteSpeed Technologies LSQUIC before 4.3.1 allows remote attackers to crash QUIC servers with crafted UDP datagrams. In lsquic_engine_packet_in, the coalesced-packet path retains packet_in structures for packets whose destination connection IDs fail validation instead of returning them through lsquic_mm_put_packet_in. Repeated pre-handshake datagrams cause linear memory growth until the exposed process becomes unresponsive or is terminated for exhausting memory.
Summary
What happened
Memory exhaustion in LiteSpeed Technologies LSQUIC before 4.3.1 allows remote attackers to crash QUIC servers with crafted UDP datagrams. In lsquic_engine_packet_in, the coalesced-packet path retains packet_in structures for packets whose destination connection IDs fail validation instead of returning them through lsquic_mm_put_packet_in. Repeated pre-handshake datagrams cause linear memory growth until the exposed process becomes unresponsive or is terminated for exhausting memory.
The record
- CVE
- CVE-2025-54939
- Published
- Aug 1, 2025
- Updated
- Aug 20, 2025
- Vendor
- LiteSpeed Technologies
- Product
- LSQUIC
- Classifications
- CWE-770, CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=0 <4.3.1
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.
Weakness, pattern, technique
Public exploit references
- PoC for QUIC-LEAKproof 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