# CVE-2026-68190: staging: rtl8723bs: fix OOB reads in rtw_get_wps_ie()

> An attacker within Wi-Fi range can trigger out-of-bounds reads in the rtl8723bs driver, potentially causing a system crash or leaking kernel memory.

- **Severity:** Not scored
- **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:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68190, DEBIAN-CVE-2026-68190, GHSA-7gch-c4xx-86rx, UBUNTU-CVE-2026-68190

## What is CVE-2026-68190?

CVE-2026-68190 is a memory corruption vulnerability in Linux, published on 10 Aug 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 rtw_get_wps_ie()

rtw_get_wps_ie() iterates over IE data from network frames without
validating that the IE header and payload fit within the remaining
buffer before reading them. Specifically:

- in_ie[cnt + 1] is read without checking cnt + 1 < in_len
- memcmp(&in_ie[cnt + 2], ...) accesses cnt + 2 without bounds check
- in_ie[cnt + 1] is used as length without verifying payload fits

Add bounds checks at the top of the loop body to break early if fewer
than 2 bytes remain for the IE header, or if the declared payload
extends past the end of the buffer. Also require at least 4 bytes of
payload before comparing the WPS OUI.

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


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

Apply the vendor's patch.

## Is CVE-2026-68190 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68190 is a memory corruption vulnerability in Linux, published on 10 Aug 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-68190 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-68190/ (Markdown: https://insights.sbomify.com/CVE-2026-68190/index.md)
```

## Sources

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

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