Kernel crash via qede ring desynchronization
Published Aug 15, 2026 · Updated Aug 15, 2026
Off-by-one buffer handling in the Linux qede driver from 4.18 allows remote attackers to crash the system via network traffic. qede_rx_build_skb() and qede_tpa_rx_build_skb() consume a buffer descriptor when qede_build_skb() returns NULL, after which their callers recycle additional descriptors and desynchronize the ring. Reachability requires qede receive processing plus an allocation failure under memory pressure; corrupted DMA page references can damage the SLUB freelist and interrupt the system.
Summary
What happened
Off-by-one buffer handling in the Linux qede driver from 4.18 allows remote attackers to crash the system via network traffic. qede_rx_build_skb() and qede_tpa_rx_build_skb() consume a buffer descriptor when qede_build_skb() returns NULL, after which their callers recycle additional descriptors and desynchronize the ring. Reachability requires qede receive processing plus an allocation failure under memory pressure; corrupted DMA page references can damage the SLUB freelist and interrupt the system.
The record
- CVE
- CVE-2026-72339
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-193, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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.18
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <07be8b8adf91b7ada4c3dacce064d572a6066421
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <0bf78df2d3ecb1f4964ff42a7327d25845955153
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <1624aa100c0b218181aa74e3696a389b509298cb
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <814a5edac8c9fc04051808d5faaa93768e989281
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <982d6d6bc059c5dff37a2201c2f08c14bcfcbd20
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <b066420e57f3402a52c998678b4678252ac9bb63
- Affected versionversion=8a8633978b842c88fbcfe00d4e5dde96048f630e <ecc05d4b20220a09c9c69584fc46ca55248a374a
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