| CVE-2024-47030 |
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ACPM component, A-315191818
|
5.1
Moyenne
|
25 oct. 2024 |
| CVE-2024-47035 |
In vring_init of external/headers/include/virtio/virtio_ring.h, there is a possible out of bounds write due to a logic…
|
7.4
Élevée
|
25 oct. 2024 |
| CVE-2024-47034 |
there is a possible out of bounds read due to a missing bounds check
|
5.1
Moyenne
|
25 oct. 2024 |
| CVE-2024-47033 |
In lwis_allocator_free of lwis_allocator.c, there is a possible memory corruption due to a use after free
|
7.4
Élevée
|
25 oct. 2024 |
| CVE-2024-47031 |
Android before 2024-10-05 on Google Pixel devices allows privilege escalation in the ABL component, A-329163861
|
7.4
Élevée
|
25 oct. 2024 |
| CVE-2024-47029 |
In TrustySharedMemoryManager::GetSharedMemory of ondevice/trusty/trusty_shared_memory_manager.cc, there is a possible…
|
5.1
Moyenne
|
25 oct. 2024 |
| CVE-2024-47028 |
In ffu_flash_pack of ffu.c, there is a possible out of bounds read due to an integer overflow
|
5.1
Moyenne
|
25 oct. 2024 |
| CVE-2024-47027 |
In sm_mem_compat_get_vmm_obj of lib/sm/shared_mem.c, there is a possible arbitrary physical memory access due to…
|
7.4
Élevée
|
25 oct. 2024 |
| CVE-2024-47026 |
In gsc_gsa_rescue of gsc_gsa.c, there is a possible out of bounds read due to an incorrect bounds check
|
5.1
Moyenne
|
25 oct. 2024 |
| CVE-2024-47025 |
In ppmp_protect_buf of drm_fw.c, there is a possible information disclosure due to a logic error in the code
|
5.1
Moyenne
|
25 oct. 2024 |
| CVE-2024-47024 |
In vring_size of external/headers/include/virtio/virtio_ring.h, there is a possible out of bounds write due to an…
|
7.4
Élevée
|
25 oct. 2024 |
| CVE-2024-47023 |
there is a possible man-in-the-middle attack due to a logic error in the code
|
7.4
Élevée
|
25 oct. 2024 |
| CVE-2024-47022 |
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ACPM component, A-331255656
|
5.1
Moyenne
|
25 oct. 2024 |
| CVE-2024-44098 |
In lwis_device_event_states_clear_locked of lwis_event.c, there is a possible privilege escalation due to a double free
|
7.4
Élevée
|
25 oct. 2024 |
| CVE-2024-32922 |
In gpu_pm_power_on_top_nolock of pixel_gpu_power.c, there is a possible compromise of protected memory due to a logic…
|
7.4
Élevée
|
13 juin 2024 |
| CVE-2024-32921 |
In lwis_initialize_transaction_fences of lwis_fence.c, there is a possible out of bounds write due to a missing bounds…
|
7.4
Élevée
|
13 juin 2024 |
| CVE-2024-32919 |
In lwis_add_completion_fence of lwis_fence.c, there is a possible escalation of privilege due to type confusion
|
7.8
Élevée
|
13 juin 2024 |
| CVE-2024-32909 |
In handle_msg of main.cpp, there is a possible out of bounds write due to a heap buffer overflow
|
8.1
Élevée
|
13 juin 2024 |
| CVE-2024-32903 |
In prepare_response_locked of lwis_transaction.c, there is a possible out of bounds write due to improper input…
|
7.4
Élevée
|
13 juin 2024 |
| CVE-2024-32893 |
In _s5e9865_mif_set_rate of exynos_dvfs.c, there is a possible out of bounds read due to improper casting
|
8.1
Élevée
|
13 juin 2024 |
| CVE-2024-29784 |
In prepare_response of lwis_periodic_io.c, there is a possible out of bounds write due to an integer overflow
|
7.7
Élevée
|
13 juin 2024 |
| CVE-2024-29753 |
In tmu_set_control_temp_step of tmu.c, there is a possible out of bounds write due to a missing bounds check
|
7.7
Élevée
|
5 avr. 2024 |
| CVE-2024-29749 |
In tmu_set_tr_thresholds of tmu.c, there is a possible out of bounds write due to a missing bounds check
|
8.4
Élevée
|
5 avr. 2024 |
| CVE-2024-29748 |
Exploitée
Android Pixel Privilege Escalation Vulnerability
|
7.8
Élevée
|
5 avr. 2024 |
| CVE-2024-29743 |
In tmu_set_temp_lut of tmu.c, there is a possible out of bounds write due to a missing bounds check
|
7.7
Élevée
|
5 avr. 2024 |