Probabilistic tracker management for memory attack mitigation
Rowhammer attacks, which are malicious processes that rapidly issue access requests to memory, can impose serious security threats including being used to tamper data, take control of entire systems, and even breach confidentiality. Current solutions to defend against these attacks are limited, as they typically employ a deterministic tracker to track the portions of memory accessed and to mitigate potential attacks accordingly. However, the deterministic nature of these trackers results in their own vulnerability. The present disclosure provides probabilistic tracker management for mitigation of rowhammer attacks and/or other memory attacks in which a row (or other defined portion of memory) is maliciously targeted to disturb contents of neighboring rows, which can prevent these types of attacks that otherwise take advantage of the determinism in prior used tracker designs.
1 . A method, comprising:
at a device:
pseudo-randomly or randomly sampling a subset of memory access requests from a stream of memory access requests issued to a memory; and
updating a data structure configured to track memory access requests for the memory, based on the subset of memory access requests sampled from the stream, wherein updating the data structure includes, for each memory access request in the subset of memory access requests:
determining whether the data structure includes an existing entry tracking accesses for a portion of the memory associated with the memory access request;
when the data structure includes the existing entry for the portion of the memory associated with the memory access request, updating an access counter included in the existing entry; and
when the data structure does not include the existing entry for the portion of the memory associated with the memory access request:
when the data structure is occupied above a threshold or is full, evicting from the data structure an existing entry tracking accesses for another portion of the memory, and
inserting a new entry in the data structure for the portion of the memory associated with the memory access request;
causing one or more attack mitigation actions to be performed, using the updated data structure.
2 . The method of claim 1 , wherein the memory is dynamic random access memory (DRAM).
3 . The method of claim 1 , wherein the stream of memory access requests is generated by monitoring the memory access requests access issued to the memory.
4 . The method of claim 1 , wherein a number of memory access requests included in the subset is preconfigured.
5 . The method of claim 1 , wherein a rate at which the stream is sampled is static.
6 . The method of claim 5 , wherein the rate at which the stream is sampled matches a rate at which memory refreshes are issued to update a state of the memory.
7 . The method of claim 1 , wherein the rate at which the data structure is updated matches a rate at which memory refreshes are issued to update a state of the memory.
8 . The method of claim 7 , wherein the rate at which the attack mitigation actions are performed is dynamic.
9 . The method of claim 1 , wherein the data structure stores a plurality of entries each indicating a different portion of the memory and a counter of a number of accesses made to the portion of the memory.
10 . The method of claim 9 , wherein a size of the data structure is preconfigured.
11 . The method of claim 9 , wherein each portion of the memory is a row in the memory.
12 . The method of claim 1 , wherein the existing entry evicted from the data structure is selected randomly.
13 . The method of claim 1 , wherein the existing entry evicted from the data structure is a function of the access counter included in the data structure.
14 . The method of claim 1 , wherein causing the one or more attack mitigation actions to be performed, using the updated data structure, includes:
selecting, based on the updated data structure, one or more portions of the memory on which to perform the one or more attack mitigation actions.
15 . The method of claim 14 , wherein the one or more portions of the memory are neighbors to at least one portion of the memory identified from the updated data structure in accordance with a policy.
16 . The method of claim 15 , wherein the at least one portion of the memory identified from the updated data structure in accordance with a policy includes a preconfigured number of portions of the memory.
17 . The method of claim 16 , wherein the policy is to identify the preconfigured number of most frequently used (MFU) portions of memory.
18 . The method of claim 14 , wherein the one or more attack mitigation actions include refreshing the one or more portions of the memory.
19 . The method of claim 1 , wherein the method is performed at least once during each memory refresh period.
20 . The method of claim 19 , wherein the one or more attack mitigation actions are a single attack mitigation action performed during the memory refresh period.
21 . The method of claim 19 , wherein one or more attack mitigation actions are two or more attack mitigation actions performed during the memory refresh period.
22 . The method of claim 1 , wherein the one or more attack mitigation actions are performed to mitigate rowhammer attacks.
23 . The method of claim 1 , wherein the one or more attack mitigation actions are performed to mitigate rowpress attacks.
24 . The method of claim 1 , wherein the device is the memory.
25 . The method of claim 1 , wherein the device is a memory controller.
26 . A memory, comprising:
a hardware buffer to track memory access requests that have been pseudo-randomly or randomly sampled from a stream of memory access requests issued to the memory; and
logic to:
(a) update the hardware buffer based on the memory access requests sampled from the stream including, for each of the memory access requests:
determining whether the hardware buffer includes an existing entry tracking accesses for a portion of the memory associated with the memory access request;
when the hardware buffer includes the existing entry for the portion of the memory associated with the memory access request, updating an access counter included in the existing entry; and
when the hardware buffer does not include the existing entry for the portion of the memory associated with the memory access request:
when the hardware buffer is occupied above a threshold or is full, evicting from the hardware buffer an existing entry tracking accesses for another portion of the memory, and
inserting a new entry in the hardware buffer for the portion of the memory associated with the memory access request, and
(b) perform one or more attack mitigation actions, using the updated hardware buffer.
27 . The memory of claim 26 , wherein the memory is DRAM.
28 . The memory of claim 26 , wherein the logic:
selects, based on the updated hardware buffer, one or more portions of the memory on which to perform the one or more attack mitigation actions, and
performs the one or more attack mitigation actions on the one or more portions of the memory.
29 . The memory of claim 28 , wherein the one or more portions of the memory are neighbors to at least one portion of the memory identified from the updated hardware buffer in accordance with a policy.
30 . The memory of claim 29 , wherein the policy is to identify a preconfigured number of most frequently used (MFU) portions of the memory.
31 . The memory of claim 26 , wherein the sampling and the performing of one or more attack mitigation actions is repeated for each refresh period configured for the memory.
32 . A memory controller that interfaces a memory, comprising:
a hardware buffer to track memory access requests that have been pseudo-randomly or randomly sampled from a stream of memory access requests issued to the memory; and
logic that:
(a) updates the hardware buffer based on the memory access requests sampled from the stream including, for each of the memory access requests:
determining whether the hardware buffer includes an existing entry tracking accesses for a portion of the memory associated with the memory access request;
when the hardware buffer includes the existing entry for the portion of the memory associated with the memory access request, updating an access counter included in the existing entry; and
when the hardware buffer does not include the existing entry for the portion of the memory associated with the memory access request:
when the hardware buffer is occupied above a threshold or is full, evicting from the hardware buffer an existing entry tracking accesses for another portion of the memory, and
inserting a new entry in the hardware buffer for the portion of the memory associated with the memory access request, and
(b) uses the updated hardware buffer to cause the memory to perform one or more attack mitigation actions.
33 . The memory controller of claim 32 , wherein the hardware buffer is implemented in static random access memory (SRAM).
34 . The memory controller of claim 32 , wherein causing the memory to perform one or more attack mitigation actions includes issuing a refresh management (RFM) command to the memory that indicates one or more portions of the memory identified from the updated hardware buffer based on a policy, wherein the memory is configured to respond to the RFM command by performing the one or more attack mitigation actions in association with the one or more portions of the memory indicated in the RFM command.
35 . The memory controller of claim 34 , wherein the one or more attack mitigation actions include refreshing one or more other portions of the memory that are neighbors to one or more portions of the memory indicated in the RFM command.