CVE-2026-33971: Samsung Exynos LTE RRC denial of service

CVE-2026-33971 · Severity: info · Published 2026-11-05

Samsung Exynos processors handle LTE mobile connectivity through an RRC (Radio Resource Control) component. Improper handling of certain messages before a device authenticates to the network can crash this component, causing the device to lose cellular service temporarily. An attacker with network access could trigger this condition to disrupt mobile connectivity.

Technologies: Samsung Exynos. Vendors: Samsung.

Quick answers

Is CVE-2026-33971 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33971 being exploited in the wild.
How severe is CVE-2026-33971?
Informational severity, published 5 November 2026.
Which products and versions are affected?
Samsung Exynos <UNKNOWN>.
Is there a fix for CVE-2026-33971?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-33971 attacked?
It is attacked over the network, in device firmware.
Am I affected by CVE-2026-33971?
Check whether you run Samsung Exynos at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the LTE RRC component where messages received before authentication are not properly validated, triggering a data abort exception. The attack vector is network-based with no authentication required. A remote attacker can send crafted LTE RRC messages to cause a denial of service on affected devices.

Affected products

  • Samsung Exynos <UNKNOWN>

Timeline

  • 2026-11-05: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.