# CVE-2026-64536: staging: rtl8723bs: fix OOB reads in is_ap_in_tkip() IE loop

> Out-of-bounds reads in the rtl8723bs Wi-Fi driver allow attackers to cause denial of service or leak kernel memory via crafted Information Elements.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-93959, BELL-CVE-2026-64536, DEBIAN-CVE-2026-64536, GHSA-rwmp-xmg8-8r93, ROOT-OS-DEBIAN-12-CVE-2026-64536, UBUNTU-CVE-2026-64536

## What is CVE-2026-64536?

CVE-2026-64536 is a high-severity memory corruption vulnerability in Linux, published on 27 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

staging: rtl8723bs: fix OOB reads in is_ap_in_tkip() IE loop

The loop in is_ap_in_tkip() iterates over IEs without verifying that
enough bytes remain before dereferencing the IE header or its payload:

- pIE->element_id and pIE->length are read without checking that
  i + sizeof(*pIE) <= ie_length, so a truncated IE at the end of the
  buffer causes an OOB read.

- For WLAN_EID_VENDOR_SPECIFIC the code compares pIE->data + 12,
  which requires pIE->length >= 16.  For WLAN_EID_RSN it compares
  pIE->data + 8, requiring pIE->length >= 12.  Neither requirement
  is checked.

Add the missing IE header and payload bounds checks and guard each
data access with an explicit pIE->length minimum, matching the
pattern established in update_beacon_info().

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-64536?


## How do I fix CVE-2026-64536?

Apply the vendor's patch.

## Is CVE-2026-64536 being exploited?

There is no known exploitation of CVE-2026-64536 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64536 and fix it if it is affected.

What it is: CVE-2026-64536 is a high-severity memory corruption vulnerability in Linux, published on 27 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64536 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64536/ (Markdown: https://insights.sbomify.com/CVE-2026-64536/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64536
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64536
- OSV: https://osv.dev/vulnerability/CVE-2026-64536

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64536/
Summaries are generated and may contain mistakes; the official description above is the record.