Filtered by vendor Samsung
Subscriptions
Total
1443 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2025-21078 | 1 Samsung | 1 Smart Switch | 2025-11-07 | 8.8 High |
| Use of insufficiently random value of secretKey in Smart Switch prior to version 3.7.68.6 allows adjacent attackers to access backup data from applications. | ||||
| CVE-2025-21079 | 1 Samsung | 2 Members, Samsung Members | 2025-11-07 | 7.1 High |
| Improper input validation in Samsung Members prior to version 5.5.01.3 allows remote attackers to connect arbitrary URL and launch arbitrary activity with Samsung Members privilege. User interaction is required for triggering this vulnerability. | ||||
| CVE-2025-21075 | 1 Samsung | 2 Android, Mobile Devices | 2025-11-07 | 4.3 Medium |
| Out-of-bounds write in libimagecodec.quram.so prior to SMR Nov-2025 Release 1 allows remote attackers to access out-of-bounds memory. | ||||
| CVE-2025-21076 | 1 Samsung | 2 Account, Notes | 2025-11-07 | 5.5 Medium |
| Improper handling of insufficient permissions or privileges in Samsung Account prior to version 15.5.00.18 allows local attackers to access data in Samsung Account. User interaction is required for triggering this vulnerability. | ||||
| CVE-2025-21077 | 1 Samsung | 2 Email, Samsung Email | 2025-11-07 | 3.3 Low |
| Improper input validation in Samsung Email prior to version 6.2.06.0 allows local attackers to launch arbitrary activity with Samsung Email privilege. | ||||
| CVE-2025-21071 | 1 Samsung | 4 Android, Mobile, Mobile Devices and 1 more | 2025-11-07 | 5.7 Medium |
| Out-of-bounds write in handling opcode in fingerprint trustlet prior to SMR Nov-2025 Release 1 allows local privileged attackers to write out-of-bounds memory. | ||||
| CVE-2025-21073 | 1 Samsung | 2 Android, Mobile Devices | 2025-11-07 | 6.8 Medium |
| Insecure default configuration in USB connection mode prior to SMR Nov-2025 Release 1 allows privileged physical attackers to access user data. User interaction is required for triggering this vulnerability. | ||||
| CVE-2025-21074 | 1 Samsung | 2 Android, Mobile Devices | 2025-11-07 | 4.3 Medium |
| Out-of-bounds read in libimagecodec.quram.so prior to SMR Nov-2025 Release 1 allows remote attackers to access out-of-bounds memory. | ||||
| CVE-2025-54335 | 1 Samsung | 11 Exynos, Exynos 1480, Exynos 1480 Firmware and 8 more | 2025-11-07 | 6.5 Medium |
| An issue was discovered in the GPU driver in Samsung Mobile Processor Exynos 1480, 2400, 1580, 2500. There is a use-after-free in the Xclipse GPU Driver. | ||||
| CVE-2025-52910 | 1 Samsung | 15 Exynos, Exynos 1280, Exynos 1280 Firmware and 12 more | 2025-11-07 | 9.8 Critical |
| An issue was discovered in the GPU in Samsung Mobile Processor and Wearable Processor Exynos 1280, 2200, 1330, 1380, 1480, 2400. A Use-After-Free leads to privilege escalation. | ||||
| CVE-2025-27374 | 1 Samsung | 26 Exynos, Exynos 1080, Exynos 1080 Firmware and 23 more | 2025-11-07 | 5.3 Medium |
| An issue was discovered in the Secure Boot component in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850, 1080, 1280, 2200, 1330, 1380, 1480, 2400. The lack of a length check leads to out-of-bounds writes. | ||||
| CVE-2024-56426 | 1 Samsung | 31 Exynos, Exynos 1080, Exynos 1080 Firmware and 28 more | 2025-11-07 | 7.5 High |
| An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, W920, W930, W1000. The lack of a length check leads to out-of-bounds writes via malformed USB packets to the target. | ||||
| CVE-2025-54327 | 1 Samsung | 12 Exynos, Exynos 1280, Exynos 1280 Firmware and 9 more | 2025-11-07 | 6.5 Medium |
| An issue was discovered in VTS in Samsung Mobile Processor and Wearable Processor Exynos 1280, 2200, 1380, W920, W930, W1000. Improper input validation in the VTS driver leads to an arbitrary write. | ||||
| CVE-2025-49494 | 1 Samsung | 20 Exynos 1280, Exynos 1280 Firmware, Exynos 1330 and 17 more | 2025-11-07 | 7.5 High |
| An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 2100, 1280, 2200, 1330, 1380, 1480, 9110, Modem 5123. Mishandling of an 5G NRMM packet leads to a Denial of Service. | ||||
| CVE-2025-54334 | 1 Samsung | 17 Exynos, Exynos 1280, Exynos 1280 Firmware and 14 more | 2025-11-07 | 7.5 High |
| An issue was discovered in the NPU driver in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, 2500. There is a NULL Pointer Dereference of hdev in the __npu_vertex_bootup function. | ||||
| CVE-2025-52513 | 1 Samsung | 9 Exynos, Exynos 1580, Exynos 1580 Firmware and 6 more | 2025-11-07 | 7.5 High |
| An issue was discovered in Samsung Mobile Processor Exynos 2400, 1580, 2500. A race condition in the HTS driver results in an out-of-bounds write, leading to a denial of service. | ||||
| CVE-2025-52512 | 1 Samsung | 9 Exynos, Exynos 1580, Exynos 1580 Firmware and 6 more | 2025-11-07 | 7.5 High |
| An issue was discovered in Samsung Mobile Processor Exynos 2400, 1580, 2500. A race condition in the HTS driver results in out-of-bounds memory access, leading to a denial of service. | ||||
| CVE-2025-54333 | 1 Samsung | 5 Exynos, Exynos 1380, Exynos 1380 Firmware and 2 more | 2025-11-07 | 5.3 Medium |
| An issue was discovered in NPU in Samsung Mobile Processor Exynos 1380 through July 2025. There is an Invalid Pointer Dereference of node in the get_vs4l_profiler_node function. | ||||
| CVE-2025-54325 | 1 Samsung | 25 Exynos, Exynos 1080, Exynos 1080 Firmware and 22 more | 2025-11-07 | 5.3 Medium |
| An issue was discovered in VTS in Samsung Mobile Processor and Wearable Processor Exynos 1080, 1280, 2200, 1380, 1480, 2400, 1580, 2500, W920, W930, W1000. A race condition in the VTS driver results in an out-of-bounds read, leading to an information leak. | ||||
| CVE-2025-54332 | 1 Samsung | 5 Exynos, Exynos 1380, Exynos 1380 Firmware and 2 more | 2025-11-07 | 7.5 High |
| An issue was discovered in NPU in Samsung Mobile Processor Exynos 1380 through July 2025. There is a NULL Pointer Dereference of profiler.node in the npu_vertex_profileoff function. | ||||