Local crash via skipped IPv6 route reference
Published Jan 27, 2020 · Updated Aug 5, 2024
Reference-counting error in the Linux kernel before 5.3.4 allows local users to crash the system through IPv6 route lookup failures. In fib6_rule_lookup, a bitwise OR test makes the no-reference predicate always false and skips dst_hold when the caller expects a retained destination reference. A low-privileged local user can trigger an IPv6 route lookup failure, causing an availability-only kernel crash without data disclosure or modification.
Summary
What happened
Reference-counting error in the Linux kernel before 5.3.4 allows local users to crash the system through IPv6 route lookup failures. In fib6_rule_lookup, a bitwise OR test makes the no-reference predicate always false and skips dst_hold when the caller expects a retained destination reference. A low-privileged local user can trigger an IPv6 route lookup failure, causing an availability-only kernel crash without data disclosure or modification.
The record
- CVE
- CVE-2019-20422
- Published
- Jan 27, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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