Kernel panic via IPv6 route-result type confusion
Published Jun 19, 2023 · Updated Mar 11, 2025
Type confusion in the Linux kernel IPv6 module before 5.2-rc1 allows local users to crash the kernel through IPv6 policy routing. fib6_rule_lookup stores either rt6_info or fib6_info in arg.result, but fib6_rule_suppress unconditionally treats the value as rt6_info. Triggering the failed lookup requires IPv6, a specific local policy rule, and a matching packet to a local IPv6 address; the bounded result is a kernel panic.
Summary
What happened
Type confusion in the Linux kernel IPv6 module before 5.2-rc1 allows local users to crash the kernel through IPv6 policy routing. fib6_rule_lookup stores either rt6_info or fib6_info in arg.result, but fib6_rule_suppress unconditionally treats the value as rt6_info. Triggering the failed lookup requires IPv6, a specific local policy rule, and a matching packet to a local IPv6 address; the bounded result is a kernel panic.
The record
- CVE
- CVE-2023-3022
- Published
- Jun 19, 2023
- Updated
- Mar 11, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-843, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2023CVE publishedPublication date reported by the CVE source.
- Mar 11, 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=Fixed in kernel 5.2-rc1
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
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