CVE-2026-36355
Heap Overflow in Realtek RTL8192CD Wi-Fi Driver
Publication date: 2026-05-05
Last updated on: 2026-05-05
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| realtek | rtl819x_jungle_sdk | to 3.4.14B (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-782 | The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL. |
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthenticated local users to read and write arbitrary kernel memory, leading to local privilege escalation to root. Such unauthorized access and potential control over sensitive system components could result in unauthorized access to personal or protected data.
Because of this, affected systems may fail to comply with security requirements mandated by common standards and regulations such as GDPR and HIPAA, which require strict access controls and protection of sensitive data.
However, the provided information does not explicitly discuss compliance impacts or specific regulatory implications.
Can you explain this vulnerability to me?
CVE-2026-36355 is a vulnerability in the Realtek rtl819x Jungle SDK affecting the rtl8192cd Wi-Fi kernel driver. The driver includes two debug IOCTL commands (0x89F5 for write_mem and 0x89F6 for read_mem) that allow direct kernel memory write and read operations.
The vulnerability exists because these debug commands are compiled into all production builds without any access control checks, bounds checks, or locking mechanisms. This means any local user with access to a wireless interface using this driver can exploit these commands to read or write arbitrary kernel memory.
This lack of validation and access control on the debug handlers enables attackers to manipulate kernel memory directly, potentially leading to local privilege escalation.
How can this vulnerability impact me? :
This vulnerability allows a local user with access to a wireless interface using the vulnerable rtl8192cd driver to read and write arbitrary kernel memory.
Exploiting this flaw can lead to local privilege escalation (LPE), where an attacker can gain root-level privileges on the affected device.
With root access, an attacker can fully control the device, potentially compromising system integrity, confidentiality, and availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the system is running a wireless interface using the Realtek rtl8192cd Wi-Fi kernel driver from the rtl819x Jungle SDK up to version 3.4.14B. Since the vulnerability involves debug IOCTLs (0x89F5 for write_mem and 0x89F6 for read_mem) that allow kernel memory read/write without access control, detection involves verifying the presence of these IOCTL handlers.
Commands to help detect the vulnerable driver include:
- Use `lsmod` or `modinfo` to check if the rtl8192cd driver is loaded: `lsmod | grep rtl8192cd` or `modinfo rtl8192cd`.
- Check the kernel messages or dmesg for rtl8192cd related logs: `dmesg | grep rtl8192cd`.
- Use `ioctl` testing tools or custom scripts to attempt invoking IOCTLs 0x89F5 and 0x89F6 on the wireless interface device node (e.g., `/dev/net/tun` or `/dev/wlan0`) to see if the debug handlers respond without access control.
Note that no official detection tools or commands are provided, so detection may require custom scripts or proof-of-concept code to test the presence and behavior of these debug IOCTLs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Restrict local user access to the wireless interface devices to trusted users only, as exploitation requires local access.
- Disable or unload the rtl8192cd Wi-Fi kernel driver if it is not essential for your system's operation.
- Apply any vendor-provided patches or updates once available, as no official fix was available at the time of disclosure.
- Monitor vendor advisories from affected OEMs such as D-Link, TOTOLINK, and Tenda for updates or workarounds.
Since the vulnerable debug IOCTLs are compiled into production builds unconditionally, a long-term fix requires vendor patches to remove or gate these debug handlers.