# CVE-2026-31626: staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify()

> Uninitialized variable in rtl8723bs driver may cause unpredictable behavior; kernel maintainers should apply the patch.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 24 Apr 2026
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-83717, BELL-CVE-2026-31626, DEBIAN-CVE-2026-31626, GHSA-cxgj-pqq4-q34h, ROOT-OS-DEBIAN-11-CVE-2026-31626, ROOT-OS-DEBIAN-12-CVE-2026-31626, ROOT-OS-UBUNTU-2204-CVE-2026-31626, ROOT-OS-UBUNTU-2404-CVE-2026-31626, UBUNTU-CVE-2026-31626

## What is CVE-2026-31626?

CVE-2026-31626 is a high-severity vulnerability in Linux kernel, published on 24 Apr 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: initialize le_tmp64 in rtw_BIP_verify()

Initialize le_tmp64 to zero in rtw_BIP_verify() to prevent using
uninitialized data.

Smatch warns that only 6 bytes are copied to this 8-byte (u64)
variable, leaving the last two bytes uninitialized:

drivers/staging/rtl8723bs/core/rtw_security.c:1308 rtw_BIP_verify()
warn: not copying enough bytes for '&le_tmp64' (8 vs 6 bytes)

Initializing the variable at the start of the function fixes this
warning and ensures predictable behavior.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-31626 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31626 is a high-severity vulnerability in Linux kernel, published on 24 Apr 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-31626 in the wild and no public exploit code.

Affected product: Linux kernel. 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-31626/ (Markdown: https://insights.sbomify.com/CVE-2026-31626/index.md)
```

## Sources

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

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