Kernel crash via stale GRO socket reference
Published May 19, 2024 · Updated Aug 5, 2026
Denial of service in affected Linux kernel releases allows local users to crash the kernel via GRO fraglist packet processing. The skb_gro_receive and skb_gro_receive_list paths clear an aggregated packet destructor but leave its socket pointer attached, so later skb_segment_list reuse prevents the packet from being orphaned. A low-privileged local user must cause fraglist GRO traffic to be segmented; the resulting skb_orphan invariant violation triggers a kernel BUG and interrupts the host.
Summary
What happened
Denial of service in affected Linux kernel releases allows local users to crash the kernel via GRO fraglist packet processing. The skb_gro_receive and skb_gro_receive_list paths clear an aggregated packet destructor but leave its socket pointer attached, so later skb_segment_list reuse prevents the packet from being orphaned. A low-privileged local user must cause fraglist GRO traffic to be segmented; the resulting skb_orphan invariant violation triggers a kernel BUG and interrupts the host.
The record
- CVE
- CVE-2024-35890
- Published
- May 19, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=5.15
- Affected versionversion=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <2eeab8c47c3c0276e0746bc382f405c9a236a5ad
- Affected versionversion=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <5b3b67f731296027cceb3efad881ae281213f86f
- Affected versionversion=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <d225b0ac96dc40d7e8ae2bc227eb2c56e130975f
- Affected versionversion=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <ed4cccef64c1d0d5b91e69f7a8a6697c3a865486
- Affected versionversion=5e10da5385d20c4bae587bc2921e5fdd9655d5fc <fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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