7322 matches found
CVE-2025-20944
Out-of-bounds read in parsing audio data in libsavsac.so prior to SMR Apr-2025 Release 1 allows local attackers to read out-of-bounds memory...
CVE-2025-20941
Improper access control in InputManager to SMR Apr-2025 Release 1 allows local attackers to access the scancode of specific input device...
CVE-2025-20934
Improper access control in Sticker Center prior to SMR Apr-2025 Release 1 allows local attackers to access image files with system privilege...
CVE-2025-20934
Improper access control in Sticker Center prior to SMR Apr-2025 Release 1 allows local attackers to access image files with system privilege...
CVE-2025-20946
Improper handling of exceptional conditions in pairing specific bluetooth devices in Galaxy Watch Bluetooth pairing prior to SMR Apr-2025 Release 1 allows local attackers to pair with specific bluetooth devices without user interaction...
CVE-2025-20950
Use of implicit intent for sensitive communication in SamsungNotes prior to version 4.4.26.45 allows local attackers to access sensitive information...
CVE-2025-20950
CVE-2025-20950 affects Samsung Notes prior to version 4.4.26.45. The root cause is the use of implicit intents for sensitive communications, enabling local attackers to access sensitive information. Documents specify affected software and a remediation path: upgrade to 4.4.26.45 or later. No expl...
CVE-2025-20948
Summary : CVE-2025-20948 describes an out-of-bounds read in the enrollment with the cdsp frame secfr trustlet on Samsung devices, affecting versions prior to the SMR Apr-2025 Release 1. Impact : local privileged attackers could read out-of-bounds memory. Affected scope : Samsung mobile devices wi...
CVE-2025-20947
CVE-2025-20947 describes improper permission handling in ClipboardService prior to SMR Apr-2025 Release 1, enabling local attackers to access image files across multiple users with user interaction required. Affected software: ClipboardService versions prior to 1.0. Root cause: insufficient privi...
CVE-2025-20945
CVE-2025-20945 concerns an improper access control in the Samsung Galaxy Watch. The issue affects Galaxy Watch versions prior to SMR Apr-2025 Release 1, enabling local attackers to access sensitive information stored on the device. The available connected sources confirm a local-attack vector and...
CVE-2025-20944
The CVE-2025-20944 entry concerns an out-of-bounds read in parsing audio data in libsavsac.so before the SMR Apr-2025 Release 1. Affected component: libsavsac.so (audio parsing). Root cause: improper bounds checking leads to reading memory outside the allocated region when processing input data. ...
CVE-2025-20944
Out-of-bounds read in parsing audio data in libsavsac.so prior to SMR Apr-2025 Release 1 allows local attackers to read out-of-bounds memory...
CVE-2025-20943
Out-of-bounds write in secfr trustlet prior to SMR Apr-2025 Release 1 allows local privileged attackers to cause memory corruption...
CVE-2025-20943
Out-of-bounds write in secfr trustlet prior to SMR Apr-2025 Release 1 allows local privileged attackers to cause memory corruption...
CVE-2025-20942
Improper Verification of Intent by Broadcast Receiver in DeviceIdService prior to SMR Apr-2025 Release 1 allows local attackers to reset OAID...
CVE-2025-20942
CVE-2025-20942 affects Samsung devices’ DeviceIdService. The issue is improper verification of intent by the Broadcast Receiver, allowing a local attacker to reset the OAID (Scoped Identifier) on devices running versions prior to the SMR Apr-2025 Release 1. The vulnerability arises from how the b...
CVE-2025-20941
Improper access control in InputManager to SMR Apr-2025 Release 1 allows local attackers to access the scancode of specific input device...
CVE-2025-20941
Improper access control in InputManager to SMR Apr-2025 Release 1 allows local attackers to access the scancode of specific input device...
CVE-2025-20941
InputManager on Samsung SMR Apr-2025 Release 1 is affected by improper access control, allowing a local attacker to access the scancode of a specific input device. The issue is described in PT-2025-15342 and is supported by CVE-2025-20941 records across multiple feeds. There are no exploit detail...