System crash via invalid AEAD cleanup
Published Aug 22, 2022 · Updated Aug 3, 2024
NULL pointer dereference in the Linux kernel before 5.12 allows local users to crash the system through an LR-WPAN key operation. The llsec_key_alloc() error path treats failed or uninitialized AEAD transform entries as valid and passes them to crypto_free_aead(). The crash requires local access to the IEEE 802.15.4 key-add path and a transform setup failure; no confidentiality or integrity impact is reported.
Summary
What happened
NULL pointer dereference in the Linux kernel before 5.12 allows local users to crash the system through an LR-WPAN key operation. The llsec_key_alloc() error path treats failed or uninitialized AEAD transform entries as valid and passes them to crypto_free_aead(). The crash requires local access to the IEEE 802.15.4 key-add path and a transform setup failure; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2021-3659
- Published
- Aug 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in Kernel 5.12
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
- syzbot crypto_destroy_tfm crash reproducerproof of concept · demonstrated
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