Kernel crash via uninitialized GUE GRO state
Published Sep 27, 2024 · Updated Aug 5, 2026
Use of uninitialized kernel state in Linux's GUE GRO receive path allows remote attackers to crash the kernel with crafted UDP traffic. When fou is NULL, gue_gro_receive takes its exit path before skb_gro_remcsum_init initializes grc, leaving cleanup to consume indeterminate state. Reachability requires a configured GUE/FOU receive path; the stale offset can cause an out-of-bounds kernel write, memory disclosure, or a kernel crash.
Summary
What happened
Use of uninitialized kernel state in Linux's GUE GRO receive path allows remote attackers to crash the kernel with crafted UDP traffic. When fou is NULL, gue_gro_receive takes its exit path before skb_gro_remcsum_init initializes grc, leaving cleanup to consume indeterminate state. Reachability requires a configured GUE/FOU receive path; the stale offset can cause an out-of-bounds kernel write, memory disclosure, or a kernel crash.
The record
- CVE
- CVE-2024-46865
- Published
- Sep 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-908, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 27, 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=0 <*
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.
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