# US 2025/0148133 A1 · Security management of ferroelectric memory device

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

- Number: US 2025/0148133 A1
- Document ID: US20250148133A1
- Status: Published application
- Kind: A1
- Application number: 19/013,585
- Filed: 2025-01-08
- Published: 2025-05-08
- Earliest claimed: 2020-12-30
- Assignees: Micron Technology, Inc.
- Applicants: Micron Technology, Inc.
- Inventors: Danilo Caraccio; Federica Cresci; Alessandro Orlando; Paolo Amato; Angelo Alberto Rovelli; Craig A. Jones; Niccolò Izzo
- Web page: https://patentgrep.com/patent/US20250148133A1

## CPC

- G06F 21/79: in semiconductor storage media, e.g. directly-addressable memories
- G06F 21/554: {involving event detection and direct action}
- G06F 21/602: {Providing cryptographic facilities or services}
- G11C 7/24: Memory cell safety or protection circuits, e.g. arrangements for preventing inadvertent reading or writing; Status cells; Test cells
- G11C 11/2273: {Reading or sensing circuits or methods}
- G11C 11/2275: {Writing or programming circuits or methods}
- G11C 11/2295: {Protection circuits or methods}
- G06F 21/107: {License processing; Key processing}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)

## Abstract

Systems, apparatuses, and methods related to security management for a ferroelectric memory device are described. An example method can include receiving, at a memory controller and from a host, a command and firmware data. The memory controller can manage a non-volatile memory device, such as a ferroelectric memory device, and the host and the memory controller can communicate using a compute express link (CXL) protocol. The command can be executed to update firmware stored on the non-volatile memory device. The method can further include accessing a first public key from the non-volatile memory device. The method can further include validating the first public key with a second public key within the firmware data. The method can further include validating the firmware data. The method can further include verifying a security version of the firmware data. The method can further include updating the non-volatile memory device with the firmware data.

## Claims

### Claim 1

A method, comprising:
receiving, at a memory controller and from a host, a command and firmware data, wherein:
the memory controller manages a first memory device using a compute express link (CXL) protocol; and
the command is executed to update firmware stored on the first memory device;
accessing a first public key from a second memory device;
validating the first public key with a second public key within the firmware data;
validating the firmware data;
verifying a security version of the firmware data; and
updating the first memory device with the firmware data.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first memory device is a non-volatile memory device and the second memory device is a volatile memory device.

### Claim 3 (depends on 2)

The method of claim 2, wherein the first memory device is a ferroelectric memory device.

### Claim 4 (depends on 1)

The method of claim 1, further comprising determining whether a slot of the first memory device identified by the command is a correct slot for updating the first memory device with the firmware data.

### Claim 5 (depends on 1)

The method of claim 1, wherein verifying the security version comprises checking a customer ID associated with the firmware data;
wherein the method further comprises terminating the update with the firmware data in response to determining that the firmware data and the customer ID do not match.

### Claim 6 (depends on 1)

The method of claim 1, wherein the validating of the firmware data is performed using an Rivest-Shamir-Adleman (RSA) operation.

### Claim 7 (depends on 1)

The method of claim 1, further comprising receiving a command from the host indicating to activate the updated firmware data.

### Claim 8

An apparatus, comprising:
a memory controller configured to manage a first memory device using a compute express link (CXL) protocol, wherein the memory controller is further configured to:
receive a command and firmware data from a host, wherein the command is executed to update firmware stored on the first memory device;
access a first public key from a second memory device;
validate the first public key with a second public key within the firmware data;
validate the firmware data;
verify a security version of the firmware data; and
update the first memory device with the firmware data.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the first public key is a public signing key accessed by reading the first public key from the first memory device.

### Claim 10 (depends on 8)

The apparatus of claim 8, wherein, in response to the first public key being accessed, the memory controller is configured to check that a target slot for the firmware update is a same slot as an active slot.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein, in response to the target slot not being the same slot as the active slot, the memory controller is configured to issue an invalid slot return code and terminate the update of the first memory device with the firmware data.

### Claim 12 (depends on 8)

The apparatus of claim 8, wherein the memory controller is further configured to validate the second public key within the firmware data by comparing the second public key with the first public key.

### Claim 13 (depends on 8)

The apparatus of claim 8, wherein the second public key is a public key from a firmware image and the first public key is a public key previously stored in the first memory device.

### Claim 14 (depends on 8)

The apparatus of claim 8, wherein, in response to updating the first memory device with the firmware data, the updated firmware is enabled via a CXL Activate command from the host.

### Claim 15

An apparatus, comprising:
a memory controller configured to manage a memory device using a compute express link (CXL) protocol, wherein the memory controller comprises:
a central controller configured to cause performance of a read operation or a write operation, or both, wherein the central controller includes:
a cache memory to store data associated with the read operation or the write operation, wherein the read operation or the write operation is executed to update firmware stored on the memory device; and
a security component configured to:
encrypt the data in response to storing the data in the memory device as part of updating the firmware stored on the memory device with the data; and
decrypt the data before the data is transferred from the memory device;
wherein the central controller is configured to randomize a cache mapping function used to store the data in the cache memory.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the central controller is configured to randomize the cache mapping function by performing a probabilistic permutation to store the data in the cache memory and retrieve the data from the cache memory.

### Claim 17 (depends on 15)

The apparatus of claim 15, wherein the memory controller is further configured to detect a cache attack on the cache memory and, in response to the detected cache attack, cause the central controller to randomize the cache mapping function.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein the memory controller is configured to detect a glitch attack using a hardware based fault injection detection.

### Claim 19 (depends on 17)

The apparatus of claim 17, wherein the memory controller is further configured to record the detected cache attack.

### Claim 20 (depends on 15)

The apparatus of claim 15, wherein the memory controller is configured to use the CXL protocol to transfer the data to the memory device from the cache memory and from the memory device to the cache memory.
