Local system crash via unchecked TIPC key length
Published Mar 30, 2021 · Updated Aug 3, 2024
Improper input validation in Linux kernel TIPC before 5.11.11 allows local users to crash the system through a crafted netlink key. The tipc_nl_retrieve_key function reads keylen before confirming that the netlink attribute contains that field and fails to reject lengths that overflow its size calculation. Low-privileged local access is sufficient to trigger an availability-only kernel crash without user interaction.
Summary
What happened
Improper input validation in Linux kernel TIPC before 5.11.11 allows local users to crash the system through a crafted netlink key. The tipc_nl_retrieve_key function reads keylen before confirming that the netlink attribute contains that field and fails to reject lengths that overflow its size calculation. Low-privileged local access is sufficient to trigger an availability-only kernel crash without user interaction.
The record
- CVE
- CVE-2021-29646
- Published
- Mar 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 30, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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