Security readout for executives and security teams
Plain-English summary
A Linux OP-TEE driver error-handling flaw can crash the kernel when device registration fails. This can interrupt systems using a trusted execution environment, but the sources do not show remote reachability or real-world attacks. The 7.8 CVSS score indicates serious potential local impact; practical risk depends on whether OP-TEE and the affected code are present.
Executive priority
Treat this as high priority for OP-TEE-dependent appliances or servers where a kernel panic would disrupt critical operations. Confirm exposure promptly and schedule supported kernel updates. It is not supported as an Internet-wide emergency because the supplied evidence shows neither remote reachability nor active exploitation.
Technical view
Commit 7269cba53d90 introduced faulty error handling during OP-TEE device registration on the TEE bus. When registration fails, the cleanup path can cause an invalid memory access and kernel panic. The CVSS vector specifies local, low-privileged access without user interaction, although the supplied description does not demonstrate attacker-controlled triggering or impacts beyond the panic.
Likely exposure
Exposure is most likely limited to Linux systems using OP-TEE and TEE bus device registration. The supplied affected-version records are difficult to interpret consistently, so vulnerability managers should map exact distribution builds and vendor backports to the listed fixes rather than relying solely on upstream version strings.
Exploitation context
CISA KEV status is false, and no supplied source reports active exploitation or a public exploit. The CVSS vector describes a local attack requiring low privileges, but the technical description only establishes that a device-registration failure can reach the faulty path. Attacker control over that failure is not established.
Researcher notes
The documented regression originates in commit 7269cba53d90 and affects an error path during supplicant-based OP-TEE device enumeration. Multiple stable-branch fixes are referenced. Evidence demonstrates an invalid access and panic, but does not establish confidentiality or integrity compromise despite the CVSS impact metrics. Exact affected-version interpretation requires vendor-specific backport analysis.
Mitigation direction
- Install a vendor-supported kernel update containing the applicable upstream stable fix or documented backport.
- Prioritize remediation on systems where OP-TEE is enabled and kernel availability is operationally important.
- Use distribution advisories to resolve ambiguous upstream version information before declaring systems affected or remediated.
- Follow vendor guidance if immediate updating is impossible; the supplied sources name no official workaround.
Validation and detection
- Inventory kernel package builds, architectures, and whether OP-TEE support is enabled or actively used.
- Confirm each vendor kernel contains an applicable listed stable commit or an explicitly documented backport.
- Review kernel logs for OP-TEE registration failures, paging faults, data aborts, or kernel Oops events.
- After updating and rebooting, verify the running kernel build and normal OP-TEE device enumeration in a safe environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-35785 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/bc40ded92af55760d12bec8222d4108de725dbe4CVE reference, Linux
- https://git.kernel.org/stable/c/4b12ff5edd141926d49c9ace4791adf3a4902fe7CVE reference, Linux
- https://git.kernel.org/stable/c/e5b5948c769aa1ebf962dddfb972f87d8f166f95CVE reference, Linux
- https://git.kernel.org/stable/c/520f79c110ff712b391b3d87fcacf03c74bc56eeCVE reference, Linux
- https://git.kernel.org/stable/c/bfa344afbe472a9be08f78551fa2190c1a07d7d3CVE reference, Linux
- https://git.kernel.org/stable/c/95915ba4b987cf2b222b0f251280228a1ff977acCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.htmlCVE reference, CVE · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.