Security readout for executives and security teams
Plain-English summary
CVE-2024-29748 is a high-severity Android kernel issue that may let a local attacker elevate privileges after user interaction. The public description is sparse, but CISA lists it as known exploited, so organizations should treat unpatched Android exposure as urgent.
Executive priority
Prioritize remediation because this is a high-impact local privilege escalation vulnerability and is listed in CISA KEV. Business urgency is highest for managed Android fleets, executives’ mobile devices, and any phones accessing sensitive enterprise data.
Technical view
The CVE describes a logic error causing a bypass condition in the Android kernel, leading to local escalation of privilege. CVSS 7.8 reflects local access, low attack complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to Android devices with affected kernel builds covered by Google or OEM security updates. The provided bundle does not identify exact device models, kernel versions, or non-Pixel OEM scope.
Exploitation context
CISA KEV inclusion supports that exploitation has occurred in the wild. The bundle does not provide exploit details, campaign context, or proof-of-concept information. User interaction is required, and the attacker path is local rather than remote network exploitation.
Researcher notes
Evidence is limited. The CVE record gives CWE-280, Android kernel impact, and CVSS details, but not the vulnerable code path, affected versions, or fixed commits. Avoid inferring scope beyond Google, Android kernel, Pixel bulletin references, and CISA KEV status.
Mitigation direction
- Review Google Pixel April 2024 security bulletin for applicable updates.
- Apply relevant Android, Pixel, OEM, or carrier security updates promptly.
- For unsupported devices, restrict sensitive access until replacement or remediation.
- Track this CVE through CISA KEV-driven remediation workflows.
- Check vendor guidance before assuming a workaround exists.
Validation and detection
- Inventory Android and Pixel devices by model, build, and patch level.
- Confirm devices have received the applicable April 2024 or later security update.
- Check MDM compliance reports for lagging or unsupported Android devices.
- Document exceptions where vendor scope or patch availability is unclear.
- Monitor CISA KEV and Google advisories for updated remediation guidance.
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.
CWE-280: 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 lookupCVE-2024-29748 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
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
CISA KEV status
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:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/pixel/2024-04-01CVE reference
- https://twitter.com/GrapheneOS/status/1775308208472813609CVE reference · issue-tracking
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-29748CVE reference · government-resource
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.
Improper Handling of Insufficient Permissions or Privileges
Improper Handling of Insufficient Permissions or Privileges represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.