Description
In multiple locations, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Published:
2026-09-15
Score:
n/a
EPSS:
n/a
KEV:
No
Impact:
n/a
Action:
n/a
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, 15 Sep 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In multiple locations, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-09-15T18:33:56.958Z
Reserved: 2026-06-23T16:08:36.835Z
Link: CVE-2026-56914
No data.
Status : Received
Published: 2026-09-15T19:17:26.410
Modified: 2026-09-15T19:17:26.410
Link: CVE-2026-56914
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.
