Description
In multiple locations, there is a possible way to modify coprocessor instruction and data memory from non-secure software due to an insecure default value. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
Published:
2026-11-10
Score:
n/a
EPSS:
n/a
KEV:
No
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
History
Tue, 10 Nov 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In multiple locations, there is a possible way to modify coprocessor instruction and data memory from non-secure software due to an insecure default value. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-11-10T19:22:47.262Z
Reserved: 2026-09-22T05:59:06.219Z
Link: CVE-2026-95404
No data.
No data.
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.