CVE-2023-3781 · Brief

CVEs like CVE-2023-3781

The records whose text reads closest to CVE-2023-3781, in the order Forge ranked them. The number on each row is Forge's similarity score. The reason under each row uses held facts only.

1. CVE-2022-203760.765
   In trusty_log_seq_start of trusty-log.c, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

2. CVE-2021-396490.768
   In regmap_exit of regmap.c, there is a possible use-after-free due to improper locking.

   Same weakness class, CWE-667.

3. CVE-2023-210000.782
   In MediaCodec.cpp, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

4. CVE-2022-264520.850
   In isp, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

5. CVE-2022-264510.855
   In ged, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

6. CVE-2023-207330.843
   In vcu, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

7. CVE-2022-217750.825
   In sched driver, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

8. CVE-2023-207370.843
   In vcu, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

9. CVE-2022-264730.816
   In vdec fmt, there is a possible use after free due to improper locking.

   Same weakness class, CWE-667.

10. CVE-2018-93440.854
    In several functions of DescramblerImpl.cpp, there is a possible use after free due to improper locking.

    Same weakness class, CWE-667; same vendor or product family, Google.

computed Similarity is computed, not recorded. Model Forge pro. Drawn from 396,235 records. Fetched 2026-10-31.