# US 2026/0086955 A1 · Randomized and safe cache architecture

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

- Number: US 2026/0086955 A1
- Document ID: US20260086955A1
- Status: Published application
- Kind: A1
- Application number: 19/339,732
- Filed: 2025-09-25
- Published: 2026-03-26
- Earliest claimed: 2024-09-25
- Assignees: CoreSecure Technologies, LLC
- Applicants: Coresecure Technologies, LLC
- Inventors: Ruby B. Lee; Guangyuan Hu
- Web page: https://patentgrep.com/patent/US20260086955A1

## CPC

- G06F 12/0895: of parts of caches, e.g. directory or tag array
- G06F 12/1416: {by checking the object accessibility, e.g. type of access defined by the memory independently of subject rights (G06F12/1458 takes precedence)}
- G06F 12/0862: with prefetch
- G06F 12/1045: associated with a data cache
- G06F 12/121: using replacement algorithms
- G06F 12/123: with age lists, e.g. queue, most recently used [MRU] list or least recently used [LRU] list
- G06F 2212/1052: Security improvement
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present disclosure provides a cache architecture comprising a cache memory having a tag storage and a data storage, a miss status holding register (MSHR) configured to track memory requests where each memory request includes a NoFill field, a safe history buffer (SHB) configured to store safe memory addresses and generate cache line fetch requests based on the stored safe memory addresses, and a cache controller configured to prevent cache fills for memory requests having the NoFill field set, send data to a processor without filling the cache memory when the NoFill field is set, and fill the cache memory with cache lines retrieved by the cache line fetch requests generated by the SHB. The cache architecture provides security against cache timing attacks by decorrelating cache fills from actual memory requests while maintaining performance through the safe history buffer mechanism.

## Claims

### Claim 1

A cache architecture, comprising:
a safe history buffer (SHB) configured to store safe memory addresses during execution of a program, and generate cache line fetch requests based on the safe memory addresses that are stored in the SHB, each safe memory address being a memory address that is authorized, no longer speculative, or not secret.

### Claim 2 (depends on 1)

The cache architecture of claim 1, further comprising a pending memory requests tracker configured to track memory requests, each memory request including a NoFill field.

### Claim 3 (depends on 2)

The cache architecture of claim 2, further comprising a cache controller configured to:
prevent cache fills for memory requests where the NoFill field is set,
send data to a processor without filling a cache memory when the NoFill field is set, and fill the cache memory with cache lines retrieved by the cache line fetch requests generated by the SHB.

### Claim 4 (depends on 1)

The cache architecture of claim 1, wherein the safe history buffer is further configured to generate a command to clear the NoFill field of a pending memory requests tracker entry when a cache line fetch request from the SHB matches an address of the pending memory requests tracker entry.

### Claim 5 (depends on 4)

The cache architecture of claim 4, wherein the command to clear the NoFill field of the pending memory requests tracker entry is propagated to a second cache to clear corresponding NoFill fields in second cache entries.

### Claim 6 (depends on 1)

The cache architecture of claim 1, wherein the SHB is configured to randomly select a safe memory address from the stored safe memory addresses.

### Claim 7 (depends on 6)

The cache architecture of claim 6, wherein the SHB is configured to generate the cache line fetch request based on a random memory line within a window of memory lines that includes the selected safe memory address.

### Claim 8 (depends on 1)

The cache architecture of claim 1, wherein the SHB is configured to generate cache line fetch requests at a constant rate independent of cache miss events.

### Claim 9 (depends on 1)

The cache architecture of claim 1, further comprising a reorder buffer (ROB) configured to mark memory instructions as unsafe or safe, wherein the SHB receives safe memory addresses from the ROB only when memory instructions are marked as safe.

### Claim 10 (depends on 1)

The cache architecture of claim 1, wherein the cache memory implements a random replacement policy for cache line evictions.

### Claim 11

A method for operating a secure cache memory system, comprising:
determining if a memory address is a safe memory address;
storing safe memory addresses in a safe history buffer (SHB); and
generating cache line fetch requests based on safe memory addresses stored in the SHB; and
filling a cache memory with cache lines retrieved by the cache line fetch requests.

### Claim 12 (depends on 11)

The method of claim 11, further comprising a step of generating a command to clear a NoFill field of a pending memory requests tracker entry together with a fetch request from the SHB.

### Claim 13 (depends on 11)

The method of claim 11, wherein the step of generating cache line fetch requests comprises randomly selecting a safe memory address from the SHB.

### Claim 14 (depends on 13)

The method of claim 13, wherein the step of generating cache line fetch requests comprises selecting a random memory line within a window of memory lines that includes the selected safe memory address.

### Claim 15 (depends on 11)

The method of claim 11, further comprising a step of marking memory instructions as unsafe or safe using a reorder buffer, wherein only safe memory addresses are stored in the SHB.

### Claim 16

A cache architecture, comprising:
a pending memory requests tracker configured to track memory requests including a NoFill field, where the NoFill field is configured to indicate whether data should be provided to the processor without filling the cache memory.

### Claim 17 (depends on 16)

The cache architecture of claim 16, further comprising:
a cache memory; and
a cache controller configured to:
prevent cache fills for memory requests having the NoFill field set;
send data to a processor without filling the cache memory when the NoFill field is set; and
fill the cache memory with cache lines retrieved by the cache line fetch requests generated by a safe history buffer (SHB).

### Claim 18 (depends on 17)

The cache architecture of claim 17, wherein for memory store requests where the NoFill field is set, preventing cache fills includes writing stored data to a buffer in the next level of cache together with the NoFill field without filling either cache level.

### Claim 19 (depends on 17)

The cache architecture of claim 17, wherein the cache memory includes a writeback buffer configured to temporarily store modified cache lines before the modified cache lines are written to the next level of the memory hierarchy, where the writeback buffer includes a NoFill field configured to prevent writebacks of security-sensitive data from filling cache lines at lower levels of the memory hierarchy.

### Claim 20

A method for securing a cache memory system, comprising:
receiving a memory request including an address and a NoFill indicator;
determining whether the NoFill indicator is set;
when the NoFill indicator is set, retrieving data from a memory hierarchy and providing the data to a processor without filling a cache memory.

### Claim 21 (depends on 20)

The method of claim 20, further comprising a step of generating a command to clear a NoFill field of a pending memory requests tracker entry, and clearing the NoFill indicator of a memory request when a fetch request from the safe history buffer matches the address of the memory request having the NoFill indicator set.
