Google

Out of bounds write in Swiftshader in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially explo

Heap buffer overflow in fingerprint recognition in Google Chrome on ChromeOS prior to 96.0.4664.45 allowed a remote atta

Type confusion in V8 in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap corrup

Use after free in storage foundation in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exp

Inappropriate implementation in service workers in Google Chrome prior to 96.0.4664.45 allowed a remote attacker who had

Inappropriate implementation in cache in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to leak cross-ori

Use after free in media in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap cor

Type confusion in V8 in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap corrup

Use after free in storage foundation in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exp

Use after free in loader in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap co

In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In apusys, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information

In apusys, there is a possible memory corruption due to a missing bounds check. This could lead to local escalation of p

In apusys, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information

In apusys, there is a possible memory corruption due to a use after free. This could lead to local escalation of privile

In apusys, there is a possible memory corruption due to a use after free. This could lead to local escalation of privile

In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In apusys, there is a possible memory corruption due to a use after free. This could lead to local escalation of privile

In apusys, there is a possible memory corruption due to a missing bounds check. This could lead to local escalation of p

In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In ccu driver, there is a possible out of bounds read due to an integer overflow. This could lead to local information d

In geniezone driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local i

In alac decoder, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local infor

In Audio Aurisys HAL, there is a possible permission bypass due to a missing permission check. This could lead to local

In ufshcd_eh_device_reset_handler of ufshcd.c, there is a possible out of bounds read due to a missing bounds check. Thi

In __configfs_open_file of file.c, there is a possible use-after-free due to improper locking. This could lead to local

Product: AndroidVersions: Android kernelAndroid ID: A-192641593References: N/A

In (TBD) of (TBD), there is a possible way to boot with a hidden debug policy due to a missing warning to the user. This

In sec_ts_parsing_cmds of (TBD), there is a possible out of bounds write due to an incorrect bounds check. This could le

In TBD of TBD, there is a possible way to access PIN protected settings bypassing PIN confirmation due to a missing perm

In (TBD) of (TBD), there is a possible out of bounds write due to a missing bounds check. This could lead to local escal

In regmap_exit of regmap.c, there is a possible use-after-free due to improper locking. This could lead to local escalat

In gadget_dev_desc_UDC_show of configfs.c, there is a possible disclosure of kernel heap memory due to a race condition.

In mon_smc_load_sp of gs101-sc/plat/samsung/exynos/soc/exynos9845/smc_booting.S, there is a possible reinitialization of

Product: AndroidVersions: Android kernelAndroid ID: A-201537251References: N/A

Product: AndroidVersions: Android kernelAndroid ID: A-199805112References: N/A

Product: AndroidVersions: Android kernelAndroid ID: A-199809304References: N/A

In ic_startRetrieveEntryValue of acropora/app/identity/ic.c, there is a possible bypass of defense-in-depth due to missi

In synchronous_process_io_entries of lwis_ioctl.c, there is a possible out of bounds write due to a race condition. This

Product: AndroidVersions: Android kernelAndroid ID: A-126949257References: N/A

In __dwc3_gadget_ep0_queue of ep0.c, there is a possible out of bounds write due to improper locking. This could lead to

In TBD of fvp.c, there is a possible way to glitch CPU behavior due to a missing permission check. This could lead to lo

In periodic_io_work_func of lwis_periodic_io.c, there is a possible out of bounds write due to a use after free. This co

In CreateDeviceInfo of trusty_remote_provisioning_context.cpp, there is a possible out of bounds read due to a missing b

In do_ipt_get_ctl and do_ipt_set_ctl of ip_tables.c, there is a possible way to leak kernel information due to uninitial

In ep_loop_check_proc of eventpoll.c, there is a possible way to corrupt memory due to a use after free. This could lead

In valid_ipc_dram_addr of cm_access_control.c, there is a possible out of bounds read due to an integer overflow. This c