Local kernel control-flow corruption via shared-memory lifetime race
Published Dec 22, 2021 · Updated Aug 4, 2024
Use-after-free in the Linux kernel TEE subsystem through 5.15.11 allows local users to corrupt kernel control flow. tee_shm_get_from_id can retrieve a shared-memory object while its sole dma-buf reference is being destroyed, then access the freed object. The published proof of concept overwrites a kernel function pointer, but requires CONFIG_PREEMPT, disabled software PAN, and a concurrent close/ioctl race.
Summary
What happened
Use-after-free in the Linux kernel TEE subsystem through 5.15.11 allows local users to corrupt kernel control flow. tee_shm_get_from_id can retrieve a shared-memory object while its sole dma-buf reference is being destroyed, then access the freed object. The published proof of concept overwrites a kernel function pointer, but requires CONFIG_PREEMPT, disabled software PAN, and a concurrent close/ioctl race.
The record
- CVE
- CVE-2021-44733
- Published
- Dec 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- pjlantz optee-qemu proof of conceptproof 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