LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68254: staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing The Extended Supported Rates (ESR) IE handling in OnBeacon accessed *(p + 1 + ielen) and *(p + 2 + ielen) without verifying that these offsets lie within the received frame buffer. A malformed beacon with an ESR IE positioned at the end of the buffer could cause an out-of-bounds read, potentially triggering a kernel panic. Add a boundary check to ensure that the ESR IE body and the subsequent bytes are within the limits of the frame before attempting to access them. This prevents OOB reads caused by malformed beacon frames.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A nearby attacker could transmit a malformed Wi-Fi beacon that causes a Linux system using the rtl8723bs wireless driver to read beyond a received frame. The documented consequence is a possible kernel panic, disrupting the device. The issue does not require credentials or user interaction, but it requires adjacent-network access and the affected driver.

Executive priority

Treat this as a high-priority availability issue for fleets using rtl8723bs, particularly embedded or operational devices where rebooting is disruptive. It is not an internet-wide remote compromise based on supplied evidence. Quickly identify affected hardware, apply supported kernel updates, and use temporary driver isolation where patching cannot occur promptly.

Technical view

OnBeacon parsed an Extended Supported Rates information element without confirming that two subsequent byte offsets remained inside the frame buffer. An ESR element placed at the buffer’s end could therefore trigger an out-of-bounds read. Linux stable commits add bounds validation before accessing those bytes. CVSS 3.1 is 7.1: adjacent, low complexity, no privileges, low confidentiality impact, and high availability impact.

Likely exposure

Exposure is limited to Linux systems using the staging rtl8723bs driver and a vulnerable kernel revision. Systems without that driver or associated hardware are unlikely to be exposed. The supplied version data is ambiguous, so inventory should rely on distributor advisories and confirmation that the relevant stable fix is present.

Exploitation context

The attack surface is local wireless range: a malicious beacon can be received without authentication or user interaction. The supplied record identifies denial of service through a possible kernel panic and limited confidentiality impact. It provides no evidence of public exploitation, and CVE-2025-68254 is not marked as CISA KEV.

Researcher notes

The vulnerable reads occur at offsets derived from the ESR information-element length. The correction verifies that the ESR body and following bytes remain within the received frame. The bundle lists multiple stable commits, likely for separate kernel branches, but does not map each commit clearly to corrected release versions. No exploit evidence or code-execution impact is supplied.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable Linux stable fix.
  • Prioritize exposed appliances or endpoints using rtl8723bs wireless hardware.
  • Disable the affected driver or wireless interface where operationally acceptable until patched.
  • Check distribution guidance for corrected package versions; the supplied version mapping is ambiguous.

Validation and detection

  • Inventory kernels, loaded drivers, and hardware to identify rtl8723bs use.
  • Confirm the installed kernel includes the applicable referenced boundary-check commit.
  • Review kernel logs for wireless parsing faults, crashes, or unexplained panics.
  • Retest affected devices after updating without transmitting malicious beacon frames.
Prepared
Confidence
high
Sources
4

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-2025-68254 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:L/I:N/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
8Source 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:L/I:N/A:H2.84.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/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, 554c0a3abf216c991c5ebddcdb2c08689ecd290bunaffected
LinuxLinux4.12, 0, 5.15.198, 6.1.160, 6.6.120, 6.12.62, 6.17.12, 6.18.1, 6.19affected
Weakness

CWE details

No CWE listed

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