1031 matches found
CVE-2023-20618
In vcu, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07519184; Issue ID: ALPS07519184...
CVE-2023-20737
In vcu, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07645149; Issue ID: ALPS07645167...
CVE-2023-20928
In bindervmaclose of binder.c, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...
CVE-2022-39131
In camera driver, there is a possible memory corruption due to improper locking. This could lead to local denial of service in kernel...
CVE-2022-21775
In sched driver, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06479032; Issue ID: ALPS06479032...
CVE-2022-26451
In ged, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07202966; Issue ID: ALPS07202966...
CVE-2021-39801
In ionioctl of ion-ioctl.c, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...
CVE-2021-39649
In regmapexit of regmap.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...
CVE-2021-39656
In configfsopenfile of file.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...
CVE-2021-39640
In dwc3gadgetep0queue of ep0.c, there is a possible out of bounds write due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...
CVE-2020-0303
In the Media extractor, there is a possible use after free due to improper locking. This could lead to remote code execution in the media extractor with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-1482232...
CVE-2020-0433
In blkmqqueuetagbusyiter of blk-mq-tag.c, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID...
CVE-2020-0243
In clearPropValue of MediaAnalyticsItem.cpp, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the media server with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions:...
CVE-2018-9439
In unregisterprothook and packetrelease of afpacket.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with System execution privileges needed. User interaction is not needed for exploitation...
CVE-2025-37969: Improper Locking
In the Linux kernel, the following vulnerability has been resolved: iio: imu: stlsm6dsx: fix possible lockup in stlsm6dsxreadtaggedfifo Prevent stlsm6dsxreadtaggedfifo from falling in an infinite loop in case patternlen is equal to zero and the device FIFO is not empty...
CVE-2025-37940: Improper Locking
In the Linux kernel, the following vulnerability has been resolved: ftrace: Add condresched to ftracegraphsethash When the kernel contains a large number of functions that can be traced, the loop in ftracegraphsethash may take a lot of time to execute. This may trigger the softlockup watchdog. Ad...
CVE-2025-1706 GPU DDK - Improper locking when accessing the pvr_exp_fence object
Software installed and run as a non-privileged user may conduct improper GPU system calls to trigger use-after-free kernel exceptions...
CVE-2025-1706 GPU DDK - Improper locking when accessing the pvr_exp_fence object
Software installed and run as a non-privileged user may conduct improper GPU system calls to trigger use-after-free kernel exceptions...
CVE-2025-20047
Intel CNVi vulnerability CVE-2025-20047 affects Intel® Integrated Connectivity I/O interface on some Core™ Ultra Processors. The root cause is improper locking in CNVi that could allow an unauthenticated attacker with physical access to escalate privileges. Impact per sources is elevation of priv...
CVE-2025-20047
Improper locking in the IntelR Integrated Connectivity I/O interface CNVi for some IntelR Core™ Ultra Processors may allow an unauthenticated user to potentially enable escalation of privilege via physical access...