Dynabook/TOSHIBA Generic IO & Memory Access Driver exposed ioctl with insufficient access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 1.77- |
Summary
A vulnerability marked as problematic has been reported in Dynabook/TOSHIBA Generic IO & Memory Access Driver. This impacts an unknown function. The manipulation leads to exposed ioctl with insufficient access control. This vulnerability is documented as CVE-2026-56129. The attack needs to be performed locally. There is not any exploit available.
Details
A vulnerability was found in Dynabook/TOSHIBA Generic IO & Memory Access Driver (the affected version is unknown) and classified as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a exposed ioctl with insufficient access control vulnerability. Using CWE to declare the problem leads to CWE-782. The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Generic IO & Memory Access driver for PCs provided by TOSHIBA CORPORATION and Dynabook Inc. exposes its IOCTL with insufficient access control. A logged-in user with no administrative privilege may access physical memory.
It is possible to read the advisory at global.sharp. The identification of this vulnerability is CVE-2026-56129 since 06/19/2026. The exploitation is known to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/25/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-39190). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.5
CNA Vector (jpcert): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Exposed ioctl with insufficient access controlCWE: CWE-782
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/19/2026 CVE reserved06/25/2026 Advisory disclosed
06/25/2026 VulDB entry created
06/25/2026 VulDB entry last update
Sources
Advisory: global.sharpStatus: Not defined
CVE: CVE-2026-56129 (🔒)
GCVE (CVE): GCVE-0-2026-56129
GCVE (VulDB): GCVE-100-373811
EUVD: 🔒
Entry
Created: 06/25/2026 12:28Updated: 06/25/2026 15:28
Changes: 06/25/2026 12:28 (72), 06/25/2026 15:28 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.