8416 matches found
Samsung Mobile Processor security vulnerabilities
SAMSUNG Mobile Processor is a family of mobile processors from the South Korean company Samsung SAMSUNG. A security vulnerability exists in SAMSUNG Mobile Processor, which originates from a reference counting error in the xclipse amdgpu driver, resulting in memory reuse after release...
CVE-2024-27365
An issue was discovered in Samsung Mobile Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxblockackind, there is no input validation check on a length coming from userspace, which can lead to ...
CVE-2024-27366
An issue was discovered in Samsung Mobile Processor, Wearable Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxscandoneind, there is no input validation check on a length coming from userspace...
CVE-2024-27368
An issue was discovered in Samsung Mobile Processor Exynos Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxreceivedframeind, there is no input validation check on a length...
CVE-2024-27387
An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. In the function slsirxrangedoneind, there is no input validation check on rttid coming from userspace, which can lead to a heap overwrite...
CVE-2024-27383
An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. In the function slsigetscanextraies, there is no input validation check on defaulties coming from userspace, which can lead to a heap overwrite...
dovecot: using a large number of address headers may trigger a denial of service
A flaw was found in Dovecot. Processing a large number of address headers From, To, Cc, Bcc, etc can be excessively CPU intensive. This flaw allows a remote attacker to trigger a denial of service...
CVE-2024-27365
An issue was discovered in Samsung Mobile Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxblockackind, there is no input validation check on a length coming from userspace, which can lead to ...
CVE-2024-27368
An issue was discovered in Samsung Mobile Processor Exynos Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxreceivedframeind, there is no input validation check on a length...
PT-2024-21855
Name of the Vulnerable Software and Affected Versions Samsung Mobile Processor Exynos Wearable Processor versions Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930 Description An issue was discovered in the function slsi rx scan ind,...
CVE-2024-27387
An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. In the function slsirxrangedoneind, there is no input validation check on rttid coming from userspace, which can lead to a heap overwrite...
CVE-2024-27364
An issue was discovered in Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxroamedind, there is no input validation check on a length coming from userspace, which can lead ...
CVE-2024-27367
An issue was discovered in Samsung Mobile Processor Exynos Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxscanind, there is no input validation check on a length coming from userspace, whi...
CVE-2024-27366
An issue was discovered in Samsung Mobile Processor, Wearable Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxscandoneind, there is no input validation check on a length coming from userspace...
CVE-2024-27383
CVE-2024-27383 affects Samsung Mobile Processor Exynos models 980, 850, 1280, 1380, and 1330. The issue resides in slsi_get_scan_extra_ies() where input validation is missing for default_ies from userspace, enabling a heap overwrite. Documents consistently describe the vulnerable component and ro...
CVE-2024-27366
An issue was discovered in Samsung Mobile Processor, Wearable Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxscandoneind, there is no input validation check on a length coming from userspace...
CVE-2024-27387
An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. In the function slsirxrangedoneind, there is no input validation check on rttid coming from userspace, which can lead to a heap overwrite...
CVE-2024-27364
An issue was discovered in Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxroamedind, there is no input validation check on a length coming from userspace, which can lead ...
CVE-2024-27364: Out-of-bounds Read
An issue was discovered in Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxroamedind, there is no input validation check on a length coming from userspace, which can lead ...
CVE-2024-27366: Out-of-bounds Read
An issue was discovered in Samsung Mobile Processor, Wearable Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsirxscandoneind, there is no input validation check on a length coming from userspace...