Google CVEs
9,109 CVEs and advisories name Google as an affected vendor, 82 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2024-6292Use after free in Dawn in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to potentially exploit heap corruption via a craft
- CVE-2024-6291Use after free in Swiftshader in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to potentially exploit heap corruption via
- CVE-2024-6290Use after free in Dawn in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to potentially exploit heap corruption via a craft
- CVE-2024-6102Out of bounds memory access in Dawn in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to potentially exploit heap corruptio
- CVE-2024-6101Inappropriate implementation in V8 in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to perform out of bounds memory access
- CVE-2024-6100Type Confusion in V8 in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to execute arbitrary code via a crafted HTML page.
- CVE-2024-6103Use after free in Dawn in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to potentially exploit heap corruption via a craft
- CVE-2024-32930In plugin_ipc_handler of slc_plugin.c, there is a possible information disclosure due to uninitialized data.
- CVE-2024-32926there is a possible information disclosure due to side channel information disclosure.
- CVE-2024-32925In dhd_prot_txstatus_process of dhd_msgbuf.c, there is a possible out of bounds write due to a missing bounds check.
- CVE-2024-32924In DeregAcceptProcINT of cn_NrmmStateDeregInit.cpp, there is a possible denial of service due to a logic error in the code.
- CVE-2024-32923there is a possible cellular denial of service due to a logic error in the code.
- CVE-2024-32922In gpu_pm_power_on_top_nolock of pixel_gpu_power.c, there is a possible compromise of protected memory due to a logic error in the code.
- CVE-2024-32921In lwis_initialize_transaction_fences of lwis_fence.c, there is a possible out of bounds write due to a missing bounds check.
- CVE-2024-32920In set_secure_reg of sac_handler.c, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-32919In lwis_add_completion_fence of lwis_fence.c, there is a possible escalation of privilege due to type confusion.
- CVE-2024-32918Permission Bypass allowing attackers to disable HDCP 2.2 encryption by not completing the HDCP Key Exchange initialization steps
- CVE-2024-32917In pl330_dma_from_peri_start() of fp_spi_dma.c, there is a possible out of bounds write due to a missing bounds check.
- CVE-2024-32916In fvp_freq_histogram_init of fvp.c, there is a possible Information Disclosure due to uninitialized data.
- CVE-2024-32915In CellInfoListParserV2::FillCellInfo() of protocolnetadapter.cpp, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-32914In tpu_get_int_state of tpu.c, there is a possible information disclosure due to uninitialized data.
- CVE-2024-32913In wl_notify_rx_mgmt_frame of wl_cfg80211.c, there is a possible out of bounds write due to an integer overflow.
- CVE-2024-32912there is a possible persistent Denial of Service due to test/debugging code left in a production build.
- CVE-2024-32911There is a possible escalation of privilege due to improperly used crypto.
- CVE-2024-32910In handle_msg_shm_map_req of trusty/user/base/lib/spi/srv/tipc/tipc.c, there is a possible stack data disclosure due to uninitialized data.
- CVE-2024-32909In handle_msg of main.cpp, there is a possible out of bounds write due to a heap buffer overflow.
- CVE-2024-32908In sec_media_protect of media.c, there is a possible permission bypass due to a race condition.
- CVE-2024-32907In memcall_add of memlog.c, there is a possible buffer overflow due to improper input validation.
- CVE-2024-32906In AcvpOnMessage of avcp.cpp, there is a possible EOP due to uninitialized data.
- CVE-2024-32905In circ_read of link_device_memory_legacy.c, there is a possible out of bounds write due to an incorrect bounds check.