Security readout for executives and security teams
Plain-English summary
A memory-safety flaw in Fuchsia’s Zircon kernel pager proxy could let an attacker move from a low-privileged user context into the kernel. Successful exploitation could compromise confidentiality, integrity, and availability. The source bundle does not establish which deployed products contain vulnerable code, and its Android F30.1.1 entry is marked unaffected.
Executive priority
Treat as a high-priority verification and patch-management issue because kernel compromise could provide full device control. Immediate emergency response is not supported by current exploitation evidence. Ask platform owners to identify Fuchsia or Zircon dependencies and follow Google’s confirmed remediation guidance promptly.
Technical view
CVE-2025-36940 is a CWE-416 use-after-free in a Zircon kernel pager proxy. It may permit userspace-to-kernel privilege escalation. CVSS 3.1 rates it 8.8, with low attack complexity, low privileges required, no user interaction, and high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is uncertain. Prioritize systems using Fuchsia or incorporating the relevant Zircon kernel pager implementation. The supplied affected-product record names Android F30.1.1 but assigns it a default status of unaffected, so it should not be treated as confirmed vulnerable without vendor clarification.
Exploitation context
The CVSS vector reports network reachability, low complexity, low privileges required, and no user interaction. However, the bundle provides no exploit prerequisites beyond those metrics. The CVE is not listed as KEV, and no supplied source supports active exploitation or public exploit availability.
Researcher notes
The public bundle is sparse and internally ambiguous: the title identifies Fuchsia, while the structured product entry names Android F30.1.1 and marks it unaffected. No vulnerable version range, fixed version, patch identifier, root-cause detail, or exploitation evidence is supplied. Avoid expanding the affected population until Google or the CVE record clarifies it.
Mitigation direction
- Review Google’s advisory for confirmed affected releases and vendor-approved remediation.
- Apply applicable vendor security updates after normal compatibility testing.
- Inventory Fuchsia and Zircon-based systems, including embedded or inherited components.
- Restrict untrusted users and workloads on potentially affected systems pending clarification.
Validation and detection
- Record operating-system builds and Zircon component versions across potentially exposed assets.
- Compare discovered versions only against Google’s confirmed affected and fixed release guidance.
- Verify Android F30.1.1 remains classified unaffected in current vendor documentation.
- Confirm deployed updates through build identifiers and approved vulnerability-scanner evidence.
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.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-36940 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
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/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://support.google.com/product-documentation/answer/17072818?hl=en&ref_topic=12974021&sjid=10451061435205708316-NCCVE reference, Google_Devices · vendor-advisory
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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.