CVE-2023-21218
First published: Mon Dec 04 2023(Updated: )
In PMRChangeSparseMemOSMem of physmem_osmem_linux.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.
Credit: security@android.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Android | ||
| Google Android |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-21218?
CVE-2023-21218 has a high severity level with a severity value of 7.
What software is affected by CVE-2023-21218?
CVE-2023-21218 affects the Google Android operating system.
How can I fix CVE-2023-21218?
To fix CVE-2023-21218, it is recommended to install the security patches provided by Google for the Android operating system.
Where can I find more information about CVE-2023-21218?
More information about CVE-2023-21218 can be found in the Android Security Bulletin for December 2023.
Are there any references related to CVE-2023-21218?
Yes, you can find references to CVE-2023-21218 in the Android Security Bulletin for December 2023.
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- collector/nvd-api
- agent/software-canonical-lookup-request
- agent/references
- agent/severity
- agent/author
- agent/tags
- agent/description
- agent/event
- collector/android-source
- source/Android
- agent/software-canonical-lookup
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- vendor/google
- canonical/google android