Kernel panic via continued use after registration failure
Published May 17, 2024 · Updated Aug 5, 2026
Improper error handling in the Linux kernel OP-TEE driver allows local users to trigger a kernel panic during TEE bus registration. When device_register() fails, optee_register_device() releases the device but continues into device attribute creation instead of returning the error. Reachability requires OP-TEE device enumeration and a failed TEE bus registration; the resulting invalid access interrupts the host.
Summary
What happened
Improper error handling in the Linux kernel OP-TEE driver allows local users to trigger a kernel panic during TEE bus registration. When device_register() fails, optee_register_device() releases the device but continues into device attribute creation instead of returning the error. Reachability requires OP-TEE device enumeration and a failed TEE bus registration; the resulting invalid access interrupts the host.
The record
- CVE
- CVE-2024-35785
- Published
- May 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-754, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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=01c13d8a95e0909f0081d6e3e8a891761992371b <4b12ff5edd141926d49c9ace4791adf3a4902fe7
- Affected versionversion=1c9561b438cbe61e78515fc7b16dc7fb8cf0b763 <e5b5948c769aa1ebf962dddfb972f87d8f166f95
- Affected versionversion=5.10.204 <5.10.215
- Affected versionversion=5.15.143 <5.15.154
- Affected versionversion=6.1.68 <6.1.84
- Affected versionversion=6.6.7 <6.6.24
- Affected versionversion=6.7
- Affected versionversion=7269cba53d906cf257c139d3b3a53ad272176bca <95915ba4b987cf2b222b0f251280228a1ff977ac
- Affected versionversion=7269cba53d906cf257c139d3b3a53ad272176bca <bfa344afbe472a9be08f78551fa2190c1a07d7d3
- Affected versionversion=a953e45ebeae9a5ce342c012f7eb2a92cc8af89b <bc40ded92af55760d12bec8222d4108de725dbe4
- Affected versionversion=d3c4786b01aad8c377718f92d6d9b15906ee0a2a <520f79c110ff712b391b3d87fcacf03c74bc56ee
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.
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