7 matches found
CVE-2020-11835
In /SM8250QMaster/android/vendor/oppocharger/oppo/chargeric/oppoda9313.c, failure to check the parameter buf in the function procworkmodewrite in procworkmodewrite causes a vulnerability...
Design/Logic Flaw
In /SM8250QMaster/android/vendor/oppocharger/oppo/oppovooc.c, the function procfastchgfwupdatewrite in procfastchgfwupdatewrite does not check the parameter len, resulting in a vulnerability...
CVE-2020-11835
In /SM8250QMaster/android/vendor/oppocharger/oppo/chargeric/oppoda9313.c, failure to check the parameter buf in the function procworkmodewrite in procworkmodewrite causes a vulnerability...
CVE-2020-11833
The CVE-2020-11833 entry concerns the Oppo charger driver component mp2650_data_log_write in the MP2650 controller code within the SM8250_Q_Master Android vendor path. The identified issue is that the function mp2650_data_log_write does not validate the len parameter, creating a potential vulnera...
CVE-2020-11832
The CVE-2020-11832 entry concerns the Oppo charger code for SM8250_Q_Master: /SM8250_Q_Master/android/vendor/oppo_charger/oppo/oppo_charger.c, specifically the functions charging_limit_current_write and charging_limit_time_write. The issue is that parameters are not validated, creating a vulnerab...
CVE-2020-11833: Out-of-bounds Write
In /SM8250QMaster/android/vendor/oppocharger/oppo/chargeric/oppomp2650.c, the function mp2650datalogwrite in mp2650datalogwrite does not check the parameter len which causes a vulnerability...
CVE-2020-11832: Out-of-bounds Write
In functions charginglimitcurrentwrite and charginglimittimewrite in /SM8250QMaster/android/vendor/oppocharger/oppo/oppocharger.c have not checked the parameters, which causes a vulnerability...