LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35693: In incfs_kill_sb of fs/incfs/vfs.c, there is a possible memory corruption due to a use after free.

In incfs_kill_sb of fs/incfs/vfs.c, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-35693 is an Android kernel use-after-free issue in Incremental FS cleanup code. The sources describe possible memory corruption that could support local privilege escalation. The available bundle does not provide CVSS, broad device impact, exploit details, or active exploitation evidence.

Executive priority

Treat this as a patch-management item for Android fleets, especially unmanaged or slow-updating devices. It does not currently show public active exploitation in the provided sources, but kernel privilege issues can become more serious when combined with another local foothold.

Technical view

The flaw is in incfs_kill_sb in fs/incfs/vfs.c. The Android source reference appears to be a kernel common commit addressing object lifetime handling. The CVE text says exploitation is local, needs System execution privileges, and requires no user interaction.

Likely exposure

Exposure is limited to Android devices using affected Android kernel code that includes the vulnerable Incremental FS implementation. The bundle names Google Android kernel but does not enumerate device models, branches, or downstream OEM status.

Exploitation context

There is no KEV listing and no cited source in the bundle showing active exploitation. The source states local escalation potential and no user interaction, but also says System execution privileges are needed, which limits confidence in practical attack reach.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed affected-version matrix is provided. Analysis should stay tied to Android kernel source history, the Pixel bulletin, and downstream OEM kernel patch status rather than assuming all Android devices are affected.

Mitigation direction

  • Review the Pixel July 2023 security bulletin for vendor-provided update guidance.
  • Apply relevant Android or OEM kernel security updates when available.
  • Check whether downstream device kernels include commit 8ff940b3513cb or equivalent fix.
  • Prioritize managed Android fleets with delayed or unsupported kernel updates.
  • Avoid inventing compensating controls; follow Google or OEM guidance.

Validation and detection

  • Inventory Android devices and kernel build provenance across the fleet.
  • Map devices to Pixel or OEM July 2023 security bulletin coverage.
  • Confirm whether affected kernels include Incremental FS and the referenced fix.
  • Review vulnerability scanner findings against actual device patch levels.
  • Track exceptions for devices without vendor update confirmation.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2023-35693 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidAndroid kernelunaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.