Vulnerabilities > Google
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-06-13 | CVE-2024-32896 | Always-Incorrect Control Flow Implementation vulnerability in Google Android there is a possible way to bypass due to a logic error in the code. | 7.8 |
2024-06-13 | CVE-2024-32897 | Out-of-bounds Read vulnerability in Google Android In ProtocolCdmaCallWaitingIndAdapter::GetCwInfo() of protocolsmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. | 5.9 |
2024-06-13 | CVE-2024-32898 | Out-of-bounds Read vulnerability in Google Android In ProtocolCellIdentityParserV4::Parse() of protocolnetadapter.cpp, there is a possible out of bounds read due to a missing bounds check. | 4.7 |
2024-06-13 | CVE-2024-32899 | Race Condition vulnerability in Google Android In gpu_pm_power_off_top_nolock of pixel_gpu_power.c, there is a possible compromise of protected memory due to a race condition. | 7.0 |
2024-06-13 | CVE-2024-32900 | Improper Locking vulnerability in Google Android In lwis_fence_signal of lwis_debug.c, there is a possible Use after Free due to improper locking. | 7.8 |
2024-06-13 | CVE-2024-32901 | Out-of-bounds Write vulnerability in Google Android In v4l2_smfc_qbuf of smfc-v4l2-ioctls.c, there is a possible out of bounds write due to a missing bounds check. | 7.8 |
2024-06-13 | CVE-2024-32902 | Unspecified vulnerability in Google Android Remote prevention of access to cellular service with no user interaction (for example, crashing the cellular radio service with a malformed packet) | 7.5 |
2024-06-13 | CVE-2024-32903 | Out-of-bounds Write vulnerability in Google Android In prepare_response_locked of lwis_transaction.c, there is a possible out of bounds write due to improper input validation. | 7.8 |
2024-06-13 | CVE-2024-32904 | Out-of-bounds Read vulnerability in Google Android In ProtocolVsimOperationAdapter() of protocolvsimadapter.cpp, there is a possible out of bounds read due to a missing bounds check. | 4.7 |
2024-06-13 | CVE-2024-32905 | Out-of-bounds Write vulnerability in Google Android In circ_read of link_device_memory_legacy.c, there is a possible out of bounds write due to an incorrect bounds check. | 9.8 |