In meta, there is a possible out of bounds write due to a missing bounds check

In apusys, there is a possible memory corruption due to use after free

In aidl, there is a possible memory corruption due to use after free

In aidl, there is a possible memory corruption due to use after free

In aidl, there is a possible escalation of privilege due to a missing permission check

In display, there is a possible escalation of privilege due to an integer overflow

In display, there is a possible out of bounds write due to a missing bounds check

In battery, there is a possible out of bounds write due to a missing bounds check

In ccci, there is a possible out of bounds write and read due to a missing bounds check

In mtee, there is a possible escalation of privilege due to a missing bounds check

In mtee, there is a possible escalation of privilege due to type confusion

In vdec, there is a possible out of bounds write due to type confusion

In venc, there is a possible out of bounds write due to type confusion

In geniezone, there is a possible escalation of privilege due to use after free

In Audio HAL, there is a possible escalation of privilege due to improper input validation

In SurfaceFlinger, there is a possible memory corruption due to use after free

In camera middleware, there is a possible escalation of privilege due to double free

In Power HAL, there is a possible out of bounds write due to a missing bounds check

In Power HAL, there is a possible escalation of privilege due to type confusion

In Audio HAL, there is a possible escalation of privilege due to use after free

In Audio HAL, there is a possible escalation of privilege due to use after free

In imgsensor, there is a possible application crash due to incorrect error handling

In Modem, there is a possible escalation of privilege due to a permissions bypass

In Telephony, there is a possible memory corruption due to a heap buffer overflow

In geniezone, there is a possible out of bounds write due to a missing bounds check

In slbc, there is a possible out of bounds write due to type confusion

In geniezone, there is a possible escalation of privilege due to a missing permission check

In geniezone, there is a possible escalation of privilege due to a missing bounds check

In display, there is a possible memory corruption due to a missing bounds check

In display, there is a possible memory corruption due to use after free

In MAE, there is a possible out of bounds write due to a missing bounds check

In MAE, there is a possible out of bounds write due to a missing bounds check

In wlan STA driver, there is a possible escalation of privilege due to a missing bounds check

In display, there is a possible out of bounds write due to a missing bounds check

In display, there is a possible escalation of privilege due to a missing bounds check

In display, there is a possible out of bounds write due to a missing bounds check

In display, there is a possible out of bounds write due to a missing bounds check

In wlan STA FW, there is a possible system becoming unresponsive due to logging

In hevc decoder, there is a possible out of bounds write due to an integer overflow

In Modem, there is a possible system crash due to incorrect error handling

In Modem, there is a possible system crash due to a heap buffer overflow

In Modem, there is a possible system crash due to a logic error

In geniezone, there is a possible out of bounds write due to a race condition

In MAE, there is a possible out of bounds write due to a race condition

In apu, there is a possible application crash due to double free

In Telephony, there is a possible information disclosure due to a missing permission check

In sec boot, there is a possible escalation of privilege due to a heap buffer overflow

In geniezone, there is a possible escalation of privilege due to a missing permission check

In HFRP, there is a possible out of bounds write due to a missing bounds check

In geniezone, there is a possible out of bounds write due to a missing bounds check