LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux Wi-Fi driver may use two bytes of uninitialized memory while verifying protected wireless management traffic. This can produce unpredictable verification behavior and potentially disrupt affected systems or weaken message integrity. Exposure requires the rtl8723bs staging driver and an adjacent network position; it is not described as remotely exploitable across the internet.

Executive priority

Prioritize affected wireless endpoints and embedded devices, especially where availability is operationally important. This is a high-severity adjacent-network issue, but the supplied evidence does not indicate active exploitation. Patch through normal expedited kernel maintenance after confirming that the vulnerable driver is present.

Technical view

In rtw_BIP_verify(), six bytes are copied into an eight-byte u64 variable, leaving two bytes uninitialized. Initializing le_tmp64 to zero makes verification deterministic. The supplied CVSS 3.1 score is 7.1, with adjacent-network access, low complexity, no privileges or user interaction, low integrity impact, high availability impact, and no confidentiality impact.

Likely exposure

Likely exposure is limited to Linux systems using the staging rtl8723bs wireless driver on an affected kernel build. Systems without this driver or compatible hardware are unlikely to be exposed. The supplied version data is ambiguous, so distribution-specific kernel package status should be confirmed with the relevant vendor.

Exploitation context

The CVSS vector requires adjacent-network access, meaning an attacker would generally need proximity or access to the same wireless environment. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public weaponization, or a proven exploitation path.

Researcher notes

The defect is an uninitialized-data use during BIP verification, identified by Smatch. The source bundle names no CWE and does not demonstrate exploitability beyond the CVSS assessment. Exact affected-version boundaries are unclear because the supplied list mixes releases and commit identifiers; validate against stable fixes and distribution backports.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix.
  • Confirm the updated kernel is active after any required restart.
  • Where patching is delayed, assess whether the rtl8723bs driver can be safely avoided.
  • Monitor Linux and distribution vendor guidance for corrected package mappings.

Validation and detection

  • Inventory systems loading or packaging the rtl8723bs staging driver.
  • Record running kernel and distribution package versions on potentially affected systems.
  • Compare each build with vendor advisories and the applicable stable kernel fix.
  • After updating, verify the running kernel contains the initialization change.
  • Confirm wireless functionality and protected management traffic remain operational.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-31626 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
10Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H2.84.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-31626Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290b, 554c0a3abf216c991c5ebddcdb2c08689ecd290bunaffected
LinuxLinux4.12, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.