CVE-2026-56129
Received Received - Intake

Memory Access Vulnerability in Toshiba Dynabook Generic IO Driver

Vulnerability report for CVE-2026-56129, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-25

Last updated on: 2026-06-25

Assigner: JPCERT/CC

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-25
Last Modified
2026-06-25
Generated
2026-07-15
AI Q&A
2026-06-25
EPSS Evaluated
2026-07-14
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
toshiba generic_io_and_memory_access_driver From 2009|end_including=2016 (exc)
dynabook generic_io_and_memory_access_driver From 2009|end_including=2016 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-782 The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability exists in the Generic IO & Memory Access driver for TOSHIBA and Dynabook PCs. It involves insufficient access control on the driver's IOCTL interface, which allows a logged-in user without administrative privileges to access physical memory.

This driver is part of a BIOS/Supervisor password configuration utility installed on PCs from 2009 to 2016.

Impact Analysis

Because a non-administrative user can access physical memory through this vulnerability, it may lead to unauthorized access to sensitive data stored in memory.

This could potentially allow attackers to read or manipulate critical system information, leading to security breaches or system compromise.

Mitigation Strategies

The recommended immediate steps to mitigate this vulnerability are to stop using the Generic IO & Memory Access driver and delete it from affected systems.

Instead of using this driver for BIOS/Supervisor password configuration, use the BIOS setup utility directly.

No updates or patches will be provided for this driver, so removal is the only effective mitigation.

Compliance Impact

This vulnerability allows a logged-in user without administrative privileges to access physical memory due to insufficient access control in the Generic IO & Memory Access driver. Such unauthorized access to physical memory could potentially lead to exposure or manipulation of sensitive data.

Because of this risk, organizations using affected Toshiba or Dynabook PCs might face challenges in maintaining compliance with data protection standards and regulations like GDPR or HIPAA, which require strict controls to prevent unauthorized access to sensitive information.

Mitigating this vulnerability by removing the driver and using BIOS setup for password configuration is recommended to reduce the risk of non-compliance.

Detection Guidance

This vulnerability involves the Generic IO & Memory Access driver exposing its IOCTL interface with insufficient access control, allowing non-administrative users to access physical memory.

Detection on a system can focus on identifying the presence of this vulnerable driver installed on PCs, especially those from 2009 to 2016.

Since the vulnerability is local and related to a driver, network detection is not applicable.

To detect the driver on a Windows system, you can use commands to list installed drivers or check for the specific driver name.

  • Use PowerShell to list drivers: Get-WmiObject Win32_PnPSignedDriver | Where-Object { $_.DeviceName -like '*Generic IO & Memory Access*' }
  • Use command prompt to query driver files: driverquery /v | findstr /i "Generic IO"

If the driver is found, it indicates the system is potentially vulnerable.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-56129. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart