CVE-2024-46920: Medium severity samsung exynos vulnerability

Published Jan 13, 2025
·
Updated

An issue was discovered in Samsung Mobile Processor Exynos 9820, 9825, 980, 990, 850, 1080, 2100, and 1280. Lack of a length check leads to a stack out-of-bounds write at loadInputBuffers.

Affected Software

17 affected components
Samsung Exynos=9820, =9825, =980, =990, =850, =1080, =2100, =1280
All of the following
Samsung Exynos 9820 Firmware
Samsung Exynos 9820
All of the following
Samsung Exynos 9825 Firmware
Samsung Exynos 9825
All of the following
Samsung Exynos 980 Firmware
Samsung Exynos 980
All of the following
Samsung Exynos 990 Firmware
Samsung Exynos 990
All of the following
Samsung Exynos 850 Firmware
Samsung Exynos 850
All of the following
Samsung Exynos 1080 Firmware
Samsung Exynos 1080
All of the following
Samsung Exynos 2100 Firmware
Samsung Exynos 2100
All of the following
Samsung Exynos 1280 Firmware
Samsung Exynos 1280

Event History

Jan 13, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-46920?

CVE-2024-46920 is considered a high severity vulnerability due to its potential to cause a stack out-of-bounds write.

2

How do I fix CVE-2024-46920?

To fix CVE-2024-46920, it is recommended to update the affected Exynos processors to the latest firmware provided by Samsung.

3

Which devices are affected by CVE-2024-46920?

CVE-2024-46920 affects devices utilizing Samsung Mobile Processor Exynos models including 9820, 9825, 980, 990, 850, 1080, 2100, and 1280.

4

What could happen if CVE-2024-46920 is exploited?

Exploitation of CVE-2024-46920 could lead to unexpected application behavior, data corruption, or system crashes.

5

Is there a workaround for CVE-2024-46920?

Currently, there are no known effective workarounds for CVE-2024-46920 other than applying the necessary firmware updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203