| CVE-2025-48568 |
In multiple locations, there is a possible lockscreen bypass due to a race condition
|
7.4
High
|
Mar 2, 2026 |
| CVE-2025-48567 |
In multiple locations, there is a possible bypass of a file path filter designed to prevent access to sensitive…
|
7.8
High
|
Mar 2, 2026 |
| CVE-2025-32313 |
In UsageEvents of UsageEvents.java, there is a possible out of bounds write due to an incorrect bounds check
|
8.4
High
|
Mar 2, 2026 |
| CVE-2024-43766 |
In multiple functions of btm_ble_sec.cc, there is a possible unencrypted communication due to Invalid error handling
|
6.5
Medium
|
Mar 2, 2026 |
| CVE-2026-0106 |
In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check
|
9.3
Critical
|
Feb 5, 2026 |
| CVE-2025-36911 |
In key-based pairing, there is a possible ID due to a logic error in the code
|
7.1
High
|
Jan 15, 2026 |
| CVE-2025-36938 |
In U-Boot of append_uint32_le(), there is a possible fault injection due to a logic error in the code
|
6.8
Medium
|
Dec 11, 2025 |
| CVE-2025-36937 |
In AudioDecoder::HandleProduceRequest of audio_decoder.cc, there is a possible out of bounds write due to an incorrect…
|
9.8
Critical
|
Dec 11, 2025 |
| CVE-2025-36936 |
In GetTachyonCommand of tachyon_server_common.h, there is a possible out of bounds write due to an integer overflow
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36935 |
In trusty_ffa_mem_reclaim of shared-mem-smcall.c, there is a possible memory corruption due to uninitialized data
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36934 |
In bigo_worker_thread of private/google-modules/video/gchips/bigo.c, there is a possible use after free due to a race…
|
7.4
High
|
Dec 11, 2025 |
| CVE-2025-36932 |
In tracepoint_msg_handler of cpm/google/lib/tracepoint/tracepoint_ipc.c, there is a possible memory overwrite due to…
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36931 |
In GetHostAddress of gxp_buffer.h, there is a possible out of bounds write due to a missing bounds check
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36930 |
In GetHostAddress of gxp_buffer.h, there is a possible out of bounds write due to a missing bounds check
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36929 |
In AreFencesRegistered of gxp_fence_manager.cc, there is a possible information leak due to improper input validation
|
5.5
Medium
|
Dec 11, 2025 |
| CVE-2025-36928 |
In GetHostAddress of gxp_buffer.h, there is a possible out of bounds write due to an incorrect bounds check
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36927 |
In GetTachyonCommand of tachyon_server_common.h, there is a possible out of bounds write due to a missing bounds check
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36925 |
In WAVES_send_data_to_dsp of libaoc_waves.c, there is a possible out of bounds write due to a missing bounds check
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36924 |
In ss_DecodeLcsAssistDataReqMsg(void) of ss_LcsManagement.c, there is a possible out of bounds write due to an incorrect…
|
8.0
High
|
Dec 11, 2025 |
| CVE-2025-36923 |
In NrmmDecoder::DecodeSORTransparentContext of cn_NrmmDecoder.cpp, there is a possible out of bounds write due to a heap…
|
8.0
High
|
Dec 11, 2025 |
| CVE-2025-36922 |
In bigo_map of bigo_iommu.c, there is a possible information disclosure due to a use after free
|
6.7
Medium
|
Dec 11, 2025 |
| CVE-2025-36921 |
In ProtocolPsUnthrottleApn() of protocolpsadapter.cpp, there is a possible out of bounds read due to a missing bounds…
|
5.5
Medium
|
Dec 11, 2025 |
| CVE-2025-36919 |
In aocc_read of aoc_channel_dev.c, there is a possible double free due to improper locking
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36918 |
In aoc_service_read_message of aoc_ipc_core.c, there is a possible out of bounds read due to improper input validation
|
7.8
High
|
Dec 11, 2025 |
| CVE-2025-36917 |
In SwDcpItg of up_L2commonPdcpSecurity.cpp, there is a possible denial of service due to an incorrect bounds check
|
6.5
Medium
|
Dec 11, 2025 |