CVE-2022-20374

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none

Published

Aug 11, 2022

Last Modified

Nov 7, 2023

Status

Rejected

• CVE-2022-20369In v4l2_m2m_querybuf of v4l2-mem2mem.c, there is a possible …6.7
• CVE-2022-2037Excessive Attack Surface in GitHub repository tooljet/toolje…8
• CVE-2022-20370Product: AndroidVersions: Android kernelAndroid ID: A-215730…7.5
• CVE-2022-20371In dm_bow_dtr and related functions of dm-bow.c, there is a …6.4
• CVE-2022-20372In exynos5_i2c_irq of (TBD), there is a possible out of boun…6.7
• CVE-2022-20373In st21nfc_loc_set_polaritymode of fc/st21nfc.c, there is a …6.4
• CVE-2022-20375In LteRrcNrProAsnDecode of LteRrcNr_Codec.c, there is a poss…7.5
• CVE-2022-20376In trusty_log_seq_start of trusty-log.c, there is a possible…6.7
• CVE-2022-20377In TBD of keymaster_ipc.cpp, there is a possible to force ga…6.7
• CVE-2022-20378Product: AndroidVersions: Android kernelAndroid ID: A-234657…9.8
• CVE-2022-20379In lwis_buffer_alloc of lwis_buffer.c, there is a possible a…6.7
• CVE-2022-20380Product: AndroidVersions: Android kernelAndroid ID: A-212625…7.5