CVE-2025-68254: staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 38292407c2bb5b2b3131aaace4ecc7a829b40b76, 502ddcc405b69fa92e0add6c1714d654504f6fd7, bb5940193d813449540d8d3a82abc045be41f48a.
Low priority for now. Upgrade to Linux Linux 38292407c2bb5b2b3131aaace4ecc7a829b40b76, 502ddcc405b69fa92e0add6c1714d654504f6fd7, bb5940193d813449540d8d3a82abc045be41f48a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before c03cb111628924827351e19baa5b073e9b0d723daffected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before bb5940193d813449540d8d3a82abc045be41f48aaffected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before c173ce97d3f0f0c0fefa39139d6d04ba60b5db22affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before d1ab7f9cee22e7b8a528da9ac953e4193b96cda5affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before 38292407c2bb5b2b3131aaace4ecc7a829b40b76affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before bf323db1d883c209880bd92f3b12503e3531c3fcaffected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before 502ddcc405b69fa92e0add6c1714d654504f6fd7affected · git
- before 4.12not affected · semver
- 5.15.198 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.12-1 | 6.17.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 6.18.2-1.1 | 6.18.2-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68252Dec 16, 2025 · misc: fastrpc: Fix dma_buf object leak in fastrpc_map_lookup0Monitor
- ← EarlierCVE-2025-68253Dec 16, 2025 · mm: don't spin in add_stack_record when gfp flags don't allow0Monitor
- Later →CVE-2025-68255Dec 16, 2025 · staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 38292407c2bb5b2b3131aaace4ecc7a829b40b76 | Vendor (CNA) |
| Linux Linux | 502ddcc405b69fa92e0add6c1714d654504f6fd7 | Vendor (CNA) |
| Linux Linux | bb5940193d813449540d8d3a82abc045be41f48a | Vendor (CNA) |
| Linux Linux | bf323db1d883c209880bd92f3b12503e3531c3fc | Vendor (CNA) |
| Linux Linux | c03cb111628924827351e19baa5b073e9b0d723d | Vendor (CNA) |
| Linux Linux | c173ce97d3f0f0c0fefa39139d6d04ba60b5db22 | Vendor (CNA) |
| Linux Linux | d1ab7f9cee22e7b8a528da9ac953e4193b96cda5 | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.18.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/502ddcc405b69fa92e0add6c1714d654504f6fd7
- git.kernel.org/stable/c/bb5940193d813449540d8d3a82abc045be41f48a
- git.kernel.org/stable/c/bf323db1d883c209880bd92f3b12503e3531c3fc
- git.kernel.org/stable/c/c03cb111628924827351e19baa5b073e9b0d723d
- git.kernel.org/stable/c/c173ce97d3f0f0c0fefa39139d6d04ba60b5db22
- git.kernel.org/stable/c/d1ab7f9cee22e7b8a528da9ac953e4193b96cda5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.