# US 2025/0094648 A1 · Memory system and method for verifying safety

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0094648 A1
- Document ID: US20250094648A1
- Status: Published application
- Kind: A1
- Application number: 18/791,691
- Filed: 2024-08-01
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: Kioxia Corporation
- Applicants: Kioxia Corporation
- Inventors: Narufumi KOYA
- Web page: https://patentgrep.com/patent/US20250094648A1

## CPC

- G06F 21/79: in semiconductor storage media, e.g. directly-addressable memories
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F 2221/2103: Challenge-response
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

According to one embodiment, a memory system includes a nonvolatile memory and a controller. The controller verifies safety of a request source requesting to write data to or read data from the nonvolatile memory using a challenge-response type attestation.

## Claims

### Claim 1

A memory system comprising:
a nonvolatile memory; and
a controller configured to verify safety of a request source requesting to write data to or read data from the nonvolatile memory using a challenge-response type attestation.

### Claim 2 (depends on 1)

The memory system of claim 1, wherein the controller is further configured to verify the safety of the request source based on a standard I/O transaction from the request source.

### Claim 3 (depends on 1)

The memory system of claim 1, wherein the controller is further configured to determine whether or not to reject a request from the request source based on at least one of the following: i) whether or not a target of the request from the request source is data that requires protection, ii) whether or not a secure path has been established with the request source, and iii) whether or not safety of the request source is verified.

### Claim 4 (depends on 3)

The memory system of claim 3, wherein, in a case where it is determined that the request from the request source should be rejected, the controller is further configured to notify the request source of the rejection of the request.

### Claim 5 (depends on 1)

The memory system of claim 1, wherein the controller is further configured to:
communicate with the request source using a protocol compliant with an NVM Express™ (NVMe™) standard; and
establish a secure path with the request source by a memory mapped I/O (MMIO) using a controller memory buffer (CMB)/persistent memory region (PMR) function supported by the NVMe™ standard.

### Claim 6 (depends on 1)

The memory system of claim 1, wherein, in a case where the safety of the request source is not verified, the controller is further configured to determine to reject the request from the request source even if a target of the request from the request source is data that does not require protection.

### Claim 7 (depends on 1)

The memory system of claim 1, wherein the controller is configured to periodically verify safety of the request source.

### Claim 8 (depends on 1)

The memory system of claim 1, wherein the nonvolatile memory includes a NAND type flash memory.

### Claim 9

A method for verifying safety of a request source configured to request processing to a memory system having a nonvolatile memory, the method comprising
verifying the safety of the request source requesting to write data to or read data from the nonvolatile memory using a challenge-response type attestation.

### Claim 10 (depends on 9)

The method of claim 9, further comprising verifying the safety of the request source based on a standard I/O transaction from the request source.

### Claim 11 (depends on 9)

The method of claim 9, further comprising determining whether or not to reject a request from the request source based on at least one of the following: i) whether or not a target of the request from the request source is data that requires protection, ii) whether or not a secure path has been established with the request source, and iii) whether or not safety of the request source is verified.

### Claim 12 (depends on 11)

The method of claim 11, further comprising, in a case where it is determined that the request from the request source should be rejected, notifying the request source of the rejection of the request.

### Claim 13 (depends on 9)

The method of claim 9, further comprising:
communicating with the request source using a protocol compliant with an NVM Express™ (NVMe™) standard; and
establishing a secure path with the request source by a memory mapped I/O (MMIO) using a controller memory buffer (CMB)/persistent memory region (PMR) function supported by the NVMe™ standard.

### Claim 14 (depends on 9)

The method of claim 9, further comprising, in a case where the safety of the request source is not verified, determining to reject the request from the request source even if a target of the request from the request source is data that does not require protection.

### Claim 15 (depends on 9)

The method of claim 9, further comprising periodically verifying safety of the request source.

### Claim 16 (depends on 9)

The method of claim 9, wherein the nonvolatile memory includes a NAND type flash memory.
