Cloudanix VulnDB

CVE-2026-53178

High · 8.1

CVSS

8.1

EPSS

0.4%

Published

Jun 25, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

Some Linux devices with a specific Realtek Wi-Fi driver can be crashed by nearby malicious wireless signals unless they receive a kernel or firmware update.

Exploitation
Adjacent Network
Attacker needs
None
Complexity
Moderate
Impact
Denial Of Service
Component
OS kernel
Class
Improper Input Validation
Remediation
Patch
Effort
Medium
Patch risk
Low

What it actually does

The flaw is an improper input validation issue in the Linux kernel staging driver for Realtek RTL8723BS wireless devices. The driver processes 802.11 management information elements and subtracts fixed offsets from an unsigned ie_length value without first confirming the value is large enough. A malformed or truncated information element can cause unsigned integer underflow, which may lead the driver to calculate an unexpectedly large length and perform out-of-bounds parsing. The most likely technical outcomes are kernel memory corruption or a kernel crash/denial of service; depending on surrounding code paths and kernel hardening, more severe impact such as privilege escalation or code execution in kernel context cannot be categorically ruled out, but no public exploit is currently known from the provided data.

Why it matters to the business

Organizations using Linux systems with the affected rtl8723bs wireless driver could experience device instability, kernel crashes, or loss of wireless connectivity if exposed to malicious or malformed Wi-Fi management traffic. The risk is lower than internet-facing vulnerabilities because exploitation typically requires wireless proximity or control of nearby Wi-Fi traffic, and the vulnerability is not currently listed in CISA KEV, is not associated with ransomware activity, has no known exploit maturity, and has a low EPSS score of 0.00205. However, affected embedded, kiosk, IoT, tablet, or field devices using this chipset may be operationally sensitive because crashes may require manual recovery.

How an attack unfolds

An attacker would need a system using the vulnerable Linux kernel driver and within range of attacker-controlled Wi-Fi management traffic, such as a malicious access point, rogue beacon/probe response source, or crafted wireless frame transmitter. The attacker crafts 802.11 management frames containing malformed information elements where the declared length is smaller than expected by the driver parsing logic. When the vulnerable rtl8723bs MLME code processes the frame, it subtracts fixed offsets from the insufficient unsigned length value, causing an underflow and an incorrect large length calculation. Subsequent parsing may read or manipulate memory outside the intended buffer, potentially causing a kernel fault, wireless driver failure, or broader system crash. Reliable exploitation beyond denial of service would depend on kernel version, compiler behavior, memory layout, driver state, and enabled kernel mitigations.

How to fix it

Apply a Linux kernel update that includes the upstream fix adding bounds checks before subtracting fixed information-element offsets in the rtl8723bs driver. Because no affected product list or exact fixed package versions were provided, use the fixed kernel packages from the relevant Linux distribution, embedded vendor, device manufacturer, or kernel branch maintainer. If immediate patching is not possible, reduce exposure by disabling the rtl8723bs wireless interface where feasible, unloading or blacklisting the rtl8723bs module if the device is not required, avoiding automatic connection to untrusted Wi-Fi networks, disabling Wi-Fi scanning on sensitive systems, and physically limiting exposure to untrusted wireless environments. For embedded or appliance platforms, obtain updated firmware or kernel images from the device vendor.

How to confirm the fix worked

Confirm remediation by verifying that systems are running a kernel build containing the rtl8723bs bounds-check fix. Check distribution security advisories, kernel changelogs, or source package patches for references to rtl8723bs, rtw_mlme, and ie_length bounds checks. On endpoints, verify whether the affected module is present or loaded using commands such as lsmod, modinfo rtl8723bs, dmesg, or equivalent endpoint inventory tooling. If the module is not present, not loaded, or the hardware is absent, practical exposure is reduced. Where source validation is possible, confirm the vulnerable subtraction operations are preceded by minimum-length checks. Functional validation should include normal Wi-Fi scanning and association testing after the update to ensure the driver remains stable.

Typical attack path

  1. Identify Linux devices using the Realtek RTL8723BS wireless chipset and the staging rtl8723bs kernel driver.
  2. Move within wireless range of the target or operate a rogue/malicious access point near the target.
  3. Transmit crafted 802.11 management frames with malformed or truncated information element lengths.
  4. Trigger the vulnerable driver parsing path in rtl8723bs MLME code when the target scans, associates, roams, or processes nearby Wi-Fi management traffic.
  5. Cause unsigned length underflow, leading to out-of-bounds parsing and likely kernel instability or denial of service.

How to detect it

Retrospective detection is difficult because malformed 802.11 management frames are usually not logged by the Linux kernel or standard endpoint telemetry. Focus on indirect evidence: kernel crash dumps, dmesg/journalctl logs, system reboots, driver resets, Wi-Fi disconnect storms, or oops/panic traces that mention rtl8723bs, rtw_mlme, information element parsing, or wireless management frame handling. Review logs around times when affected devices were in public or untrusted wireless environments. If wireless monitoring infrastructure is available, examine packet captures for malformed beacon, probe response, association, or reassociation frames with inconsistent information element lengths near affected devices. Absence of logs does not prove absence of exploitation, especially if crashes disabled logging or the device rebooted without persistent journal storage.

  • rtl8723bs
  • rtw_mlme
  • ie_length
  • rtw_get_ie
  • rtw_ieee802_11_parse_elems
  • kernel BUG
  • Oops:
  • general protection fault
  • BUG: unable to handle kernel
  • Kernel panic
  • modprobe rtl8723bs
  • /lib/modules/*/kernel/drivers/staging/rtl8723bs/
  • drivers/staging/rtl8723bs/core/rtw_mlme.c

What your security team should do

  • Inventory Linux systems, appliances, and embedded devices that use the Realtek RTL8723BS chipset or load the rtl8723bs kernel module.
  • Prioritize patching for mobile, kiosk, IoT, manufacturing, healthcare, field, or remote-access devices that rely on Wi-Fi and may operate in untrusted physical locations.
  • Apply vendor-provided kernel, firmware, or OS updates containing the rtl8723bs MLME bounds-check fix.
  • Where patching is delayed, disable or blacklist the rtl8723bs module on systems that do not require this wireless adapter.
  • Avoid use of untrusted Wi-Fi networks and restrict automatic Wi-Fi scanning or auto-join behavior on affected systems until patched.
  • Monitor kernel logs for crashes, oops reports, driver resets, or repeated wireless failures involving rtl8723bs after exposure to unknown Wi-Fi environments.
  • Treat exploitation likelihood as currently low because there is no known public exploit, no KEV listing, no ransomware association, and low EPSS, but do not defer remediation indefinitely because wireless-adjacent kernel bugs can affect availability and device safety.

The record

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction Add guards to ensure ie_length is large enough before subtracting fixed IE offsets to prevent unsigned integer underflow.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities