In the Linux kernel, the following vulnerability has been resolved:
tee: optee: Fix kernel panic caused by incorrect error handling
The error path while failing to register devices on the TEE bus has a
bug leading to kernel panic as follows:
[ 15.398930] Unable to handle kernel paging request at virtual address ffff07ed00626d7c
[ 15.406913] Mem abort info:
[ 15.409722] ESR = 0x0000000096000005
[ 15.413490] EC = 0x25: DABT (current EL), IL = 32 bits
[ 15.418814] SET = 0, FnV = 0
[ 15.421878] EA = 0, S1PTW = 0
[ 15.425031] FSC = 0x05: level 1 translation fault
[ 15.429922] Data abort info:
[ 15.432813] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
[ 15.438310] CM = 0, WnR = 0, TnD = 0, TagAccess = 0
[ 15.443372] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[ 15.448697] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000d9e3e000
[ 15.455413] [ffff07ed00626d7c] pgd=1800000bffdf9003, p4d=1800000bffdf9003, pud=0000000000000000
[ 15.464146] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP
Commit 7269cba53d90 ("tee: optee: Fix supplicant based device enumeration")
lead to the introduction of this bug. So fix it appropriately.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can trigger a kernel panic when OP-TEE device registration fails. In business terms, affected systems that use the OP-TEE trusted execution environment could crash during this error path, causing availability impact. The provided sources do not show data theft, privilege escalation, or confirmed active exploitation.
Executive priority
Treat this as a targeted availability issue rather than a broad internet-facing emergency. Patch on normal security maintenance timelines, with higher priority for appliances, embedded systems, or production ARM platforms that rely on OP-TEE.
Technical view
CVE-2024-35785 is an OP-TEE TEE bus error-handling bug introduced by commit 7269cba53d90. When device registration fails, incorrect cleanup can lead to an invalid memory access and kernel oops/panic. The Linux stable tree references multiple fixing commits across supported branches.
Likely exposure
Exposure is most likely on Linux systems with OP-TEE support enabled, commonly ARM-based platforms using a Trusted Execution Environment. The bundle lists Linux kernel affected ranges but provides incomplete normalized version status, so confirm against kernel vendor advisories and deployed kernel builds.
Exploitation context
The source bundle does not cite CISA KEV listing, public exploitation, exploit code, or remote attack details. Evidence supports an availability risk from a kernel panic in a specific OP-TEE error path, not active exploitation.
Researcher notes
The bundle identifies the bug origin and crash mode but lacks CVSS, CWE, exploitability analysis, and complete normalized affected-version semantics. Further analysis should inspect the linked stable commits and downstream distribution advisories for exact branch fix levels.
Mitigation direction
Update affected Linux kernels using vendor or distribution security packages.
Check Debian LTS guidance if running Debian LTS kernels.
Prioritize systems using OP-TEE or ARM trusted execution features.
Review Linux stable commits referenced by the CVE for branch-specific fixes.
If patching is delayed, monitor affected systems for kernel oops or panic events.
Validation and detection
Inventory Linux kernel versions across ARM and OP-TEE-enabled assets.
Confirm whether OP-TEE and TEE bus support are enabled in deployed kernels.
Compare deployed kernels against vendor advisories and stable fix commits.
Review boot and kernel logs for OP-TEE registration failures or panics.
Verify updated kernels include the referenced stable fixes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35785 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.