Samsung hasn’t patched a critical bug affecting many Galaxy phones with Exynos chips
Last updated: March 17th, 2023 at 08:55 UTC+01:00
Google’s Project Zero security research team has found 18 vulnerabilities in Samsung phones powered by the Exynos chip. Notably, the vulnerabilities give hackers a free way to access your phones with the help of your phone number. According to a blog post, a bunch of Samsung Galaxy S, M, and A series phones are prone to these 18 vulnerabilities.
Security researchers do not disclose the vulnerabilities until after they are resolved. Project Zero researcher Maddie Stone tweeted that Samsung is still not concerned about this exploit, and affected phones still don’t have patches 90 days after the report. As per the researchers, not only Galaxy S, M, and A series phones but also some Vivo and Pixel 6 and 7 series phones are also affected by this Exynos chip vulnerability.
Critical bug affecting Galaxy phones using Exynos chips are related to VoWiFi and VoLTE
Galaxy phones that are affected by the Exynos chip vulnerability are the Galaxy S22, Galaxy M33, Galaxy M13, Galaxy M12, Galaxy A71, Galaxy A53, Galaxy A33, Galaxy A21, Galaxy A13, Galaxy A12, and Galaxy A04 series. Also, any wearables that use the Exynos W920 chipset or any vehicles that use the Exynos Auto T5123 chipset are also exposed to hackers thanks to the Exynos chip vulnerability.
The good news for owners of the Pixel 7 series is that Google has already patched this issue in its March security update. The update, however, hasn’t reached the Pixel 6, Pixel 6 Pro, and Pixel 6a.
Coming back to Samsung, if you have any of the above-mentioned Galaxy phones, then it is advised that you disable the Wi-Fi calling feature and the VoLTE (Voice-over-LTE) feature on your phones. Also, you should frequently check for the latest security update and, if available, install it right away.
Last updated: March 17th, 2023 at 08:55 UTC+01:00
Google’s Project Zero security research team has found 18 vulnerabilities in Samsung phones powered by the Exynos chip. Notably, the vulnerabilities give hackers a free way to access your phones with the help of your phone number. According to a blog post, a bunch of Samsung Galaxy S, M, and A series phones are prone to these 18 vulnerabilities.
Security researchers do not disclose the vulnerabilities until after they are resolved. Project Zero researcher Maddie Stone tweeted that Samsung is still not concerned about this exploit, and affected phones still don’t have patches 90 days after the report. As per the researchers, not only Galaxy S, M, and A series phones but also some Vivo and Pixel 6 and 7 series phones are also affected by this Exynos chip vulnerability.
Critical bug affecting Galaxy phones using Exynos chips are related to VoWiFi and VoLTE
Galaxy phones that are affected by the Exynos chip vulnerability are the Galaxy S22, Galaxy M33, Galaxy M13, Galaxy M12, Galaxy A71, Galaxy A53, Galaxy A33, Galaxy A21, Galaxy A13, Galaxy A12, and Galaxy A04 series. Also, any wearables that use the Exynos W920 chipset or any vehicles that use the Exynos Auto T5123 chipset are also exposed to hackers thanks to the Exynos chip vulnerability.
The good news for owners of the Pixel 7 series is that Google has already patched this issue in its March security update. The update, however, hasn’t reached the Pixel 6, Pixel 6 Pro, and Pixel 6a.
Coming back to Samsung, if you have any of the above-mentioned Galaxy phones, then it is advised that you disable the Wi-Fi calling feature and the VoLTE (Voice-over-LTE) feature on your phones. Also, you should frequently check for the latest security update and, if available, install it right away.
Denial of responsibility! Techno Blender is an automatic aggregator of the all world’s media. In each content, the hyperlink to the primary source is specified. All trademarks belong to their rightful owners, all materials to their authors. If you are the owner of the content and do not want us to publish your materials, please contact us by email – [email protected]. The content will be deleted within 24 hours.