CVE-2025-68256: staging: rtl8723bs: fix out-of-bounds read in rtw_get_ie() parser
Noroxi assessment
Priority: Monitor (action score 35/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 154828bf9559b9c8421fc2f0d7f7f76b3683aaed, 30c558447e90935f0de61be181bbcedf75952e00, 9829c6e1b2e4180fd18315252ad6faeab6128076.
Low priority for now. Upgrade to Linux Linux 154828bf9559b9c8421fc2f0d7f7f76b3683aaed, 30c558447e90935f0de61be181bbcedf75952e00, 9829c6e1b2e4180fd18315252ad6faeab6128076 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 rtw_get_ie() parser The Information Element (IE) parser rtw_get_ie() trusted the length byte of each IE without validating that the IE body (len bytes after the 2-byte header) fits inside the remaining frame buffer. A malformed frame can advertise an IE length larger than the available data, causing the parser to increment its pointer beyond the buffer end. This results in out-of-bounds reads or, depending on the pattern, an infinite loop. Fix by validating that (offset + 2 + len) does not exceed the limit before accepting the IE or advancing to the next element. This prevents OOB reads and ensures the parser terminates safely on malformed frames.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- 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 9829c6e1b2e4180fd18315252ad6faeab6128076affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before b977eb31802817f4a37da95bf16bfdaa1eeb5fc2affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before 30c558447e90935f0de61be181bbcedf75952e00affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before a54e2b2db1b7de2e008b4f62eec35aaefcc663c5affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before df191dd9f4c7249d98ada55634fa8ac19089b8cbaffected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before c0d93d69e1472ba75b78898979b90a98ba2a2501affected · git
- 554c0a3abf216c991c5ebddcdb2c08689ecd290b and later · before 154828bf9559b9c8421fc2f0d7f7f76b3683aaedaffected · git
- before 4.12not affected · semver
- 5.15.203 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-68254Dec 16, 2025 · staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing28Monitor
- ← EarlierCVE-2025-68255Dec 16, 2025 · staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing35Monitor
- Later →CVE-2025-68257Dec 16, 2025 · comedi: check device's attached status in compat ioctls0Monitor
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 | 154828bf9559b9c8421fc2f0d7f7f76b3683aaed | Vendor (CNA) |
| Linux Linux | 30c558447e90935f0de61be181bbcedf75952e00 | Vendor (CNA) |
| Linux Linux | 9829c6e1b2e4180fd18315252ad6faeab6128076 | Vendor (CNA) |
| Linux Linux | a54e2b2db1b7de2e008b4f62eec35aaefcc663c5 | Vendor (CNA) |
| Linux Linux | b977eb31802817f4a37da95bf16bfdaa1eeb5fc2 | Vendor (CNA) |
| Linux Linux | c0d93d69e1472ba75b78898979b90a98ba2a2501 | Vendor (CNA) |
| Linux Linux | df191dd9f4c7249d98ada55634fa8ac19089b8cb | 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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/30c558447e90935f0de61be181bbcedf75952e00
- git.kernel.org/stable/c/9829c6e1b2e4180fd18315252ad6faeab6128076
- git.kernel.org/stable/c/a54e2b2db1b7de2e008b4f62eec35aaefcc663c5
- git.kernel.org/stable/c/b977eb31802817f4a37da95bf16bfdaa1eeb5fc2
- git.kernel.org/stable/c/c0d93d69e1472ba75b78898979b90a98ba2a2501
- git.kernel.org/stable/c/df191dd9f4c7249d98ada55634fa8ac19089b8cb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.