CVE-2026-48175: Samsung Semiconductor RRC message out-of-bounds read

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

Samsung semiconductor components fail to properly validate RRC (Radio Resource Control) messages, which can lead to an out-of-bounds memory read. An attacker with network access to a device using the affected component could trigger this vulnerability to cause a denial-of-service condition, rendering the device temporarily unavailable.

Vendors: Samsung.

Quick answers

Is CVE-2026-48175 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-48175 being exploited in the wild.
How severe is CVE-2026-48175?
Informational severity, published 5 November 2026.
Which products and versions are affected?
Samsung Semiconductor components.
Is there a fix for CVE-2026-48175?
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-48175 attacked?
It is attacked over the network.
Am I affected by CVE-2026-48175?
Check whether you run Samsung Semiconductor components. 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 RRC message processing within Samsung semiconductor components, where malformed input fails proper bounds checking, resulting in an out-of-bounds read. Attack requires network-level access to send crafted RRC messages. Successful exploitation leads to denial-of-service via crash or resource exhaustion, though the advisory reports no known active exploitation.

Affected products

  • Samsung Semiconductor components

References

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