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-29744In tmu_get_gov_time_windows, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-29743In tmu_set_temp_lut of tmu.c, there is a possible out of bounds write due to a missing bounds check.
- CVE-2024-29742In apply_minlock_constraint of dvfs.c, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-29741In pblS2mpuResume of s2mpu.c, there is a possible mitigation bypass due to a logic error in the code.
- CVE-2024-29740In tmu_set_table of tmu.c, there is a possible out of bounds write due to a missing bounds check.
- CVE-2024-29739In tmu_get_temp_lut of tmu.c, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-29738In gov_init, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-27232In asn1_ec_pkey_parse of asn1_common.c, there is a possible OOB read due to a missing null check.
- CVE-2024-27231In tmu_get_tr_stats of tmu.c, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-22004Unchecked length in Trusted Application on Google Nest Wifi Pro, leading to out of bounds read
- CVE-2023-48426Chromecast Bootloader & Kernel-level code-execution including compromise of user-data
- CVE-2024-2887Type Confusion in WebAssembly in Google Chrome prior to 123.0.6312.86 allowed a remote attacker to execute arbitrary code via a crafted HTML
- CVE-2024-2886Use after free in WebCodecs in Google Chrome prior to 123.0.6312.86 allowed a remote attacker to perform arbitrary read/write via a crafted
- CVE-2024-2885Use after free in Dawn in Google Chrome prior to 123.0.6312.86 allowed a remote attacker to potentially exploit heap corruption via a crafte
- CVE-2024-2883Use after free in ANGLE in Google Chrome prior to 123.0.6312.86 allowed a remote attacker to potentially exploit heap corruption via a craft
- CVE-2024-2631Inappropriate implementation in iOS in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to perform UI spoofing via a crafted H
- CVE-2024-2630Inappropriate implementation in iOS in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to leak cross-origin data via a crafte
- CVE-2024-2629Incorrect security UI in iOS in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to perform UI spoofing via a crafted HTML pag
- CVE-2024-2628Inappropriate implementation in Downloads in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to perform UI spoofing via a cra
- CVE-2024-2627Use after free in Canvas in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to potentially exploit heap corruption via a craf
- CVE-2024-2626Out of bounds read in Swiftshader in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to perform out of bounds memory access v
- CVE-2024-2625Object lifecycle issue in V8 in Google Chrome prior to 123.0.6312.58 allowed a remote attacker to potentially exploit object corruption via
- CVE-2024-2400Use after free in Performance Manager in Google Chrome prior to 122.0.6261.128 allowed a remote attacker to potentially exploit heap corrupt
- CVE-2024-27237In wipe_ns_memory of nsmemwipe.c, there is a possible incorrect size calculation due to a logic error in the code.
- CVE-2024-27236In aoc_unlocked_ioctl of aoc.c, there is a possible memory corruption due to type confusion.
- CVE-2024-27235In plugin_extern_func of , there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-27234In fvp_set_target of fvp.c, there is a possible out of bounds read due to a missing bounds check.
- CVE-2024-27233In ppcfw_init_secpolicy of ppcfw.c, there is a possible permission bypass due to uninitialized data.
- CVE-2024-27230In ProtocolPsKeepAliveStatusAdapter::getCode() of protocolpsadapter.cpp, there is a possible out of bounds read due to a missing bounds chec
- CVE-2024-27229In ss_SendCallBarringPwdRequiredIndMsg of ss_CallBarring.c, there is a possible null pointer deref due to a missing null check.