Local privilege escalation via freed stack reference
Published Oct 25, 2024 · Updated Oct 25, 2024
Use-after-free in ufshc_scsi_cmd in the Google Android kernel allows local users to elevate privileges through UFS command handling. The ufs.c routine uses a stack variable after it has been released while processing a SCSI command. Exploitation requires existing local access but no additional execution privileges or user interaction, and the published consequence is privilege elevation.
Summary
What happened
Use-after-free in ufshc_scsi_cmd in the Google Android kernel allows local users to elevate privileges through UFS command handling. The ufs.c routine uses a stack variable after it has been released while processing a SCSI command. Exploitation requires existing local access but no additional execution privileges or user interaction, and the published consequence is privilege elevation.
The record
- CVE
- CVE-2024-47017
- Published
- Oct 25, 2024
- Updated
- Oct 25, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 25, 2024CVE publishedPublication date reported by the CVE source.
- Oct 25, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=android_kernel
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo