]> 2026-09-08T17:23:17+09:00 Lesson:moat securely mitigating rowhammer with per row activation counters 6e5ed0e1 3000 ko DDR5 PRAC/ABO RowHammer mitigation designs. Limits: Security bound depends on timing and threshold assumptions; evaluation is simulation/workload based and must track JEDEC/device implementation details. MOAT uses an eligibility threshold for proactive mitigation, an ALERT threshold for ABO, highest-count row tracking, and safe counter reset around refresh. S3ResearchAgent low Venue: ASPLOS. Year: 2025. PRAC+ABO specifies mechanisms, not a secure policy; Panopticon's queue can be manipulated by crafted activation patterns. Verification: full_text; confidence=high. 2026-07-16T14:58:25Z 2461238.1239005 MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters. ASPLOS 2025. Accurate per-row counters are insufficient unless queue service, delayed alerts, and reset semantics are included in the security proof. MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters workloads=SPEC CPU; GAP graph workloads; Jailbreak and performance attacks; baselines=Panopticon; PRAC+ABO configurations; metrics=maximum aggressor activations; safe TRH; slowdown; SRAM overhead; results=Panopticon reaches 1,150 activations at threshold 128; MOAT ATH=64 safe for TRH=99; 0.28% average slowdown; 7 bytes SRAM per bank Can DDR5 per-row activation counting and ALERT back-off be implemented with provable RowHammer security and low overhead? lab Prove the complete mitigation state machine against adversarial scheduling, including backpressure and counter reset. Draft 2026-07-18T14:58:47Z 2461240.1241551 2026-07-18T14:58:47Z 2461240.1241551 moat securely mitigating rowhammer with per row activation counters 6e5ed0e1 3000 ev_6fbdb1b582084fad 2026-07-16T14:58:26Z 2461238.123912 S3ResearchAgent MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters. ASPLOS 2025. paper Bibliographic paper record. not_recorded moat securely mitigating rowhammer with per row activation counters 6e5ed0e1# d556ad9dfef95a3b94db49f4ef099dd9 3000 verified-content-v1-0106 2026-07-16T18:55:56Z 2461238.2888426 S3ResearchAgent Moinuddin Qureshi et al., "MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters", ASPLOS 2025. paper Verification: full_text; confidence=high. Canonical title: MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters Question: Can DDR5 per-row activation counting and ALERT back-off be implemented with provable RowHammer security and low overhead? Context: PRAC+ABO specifies mechanisms, not a secure policy; Panopticon's queue can be manipulated by crafted activation patterns. Method: MOAT uses an eligibility threshold for proactive mitigation, an ALERT threshold for ABO, highest-count row tracking, and safe counter reset around refresh. Evaluation: workloads=SPEC CPU; GAP graph workloads; Jailbreak and performance attacks; baselines=Panopticon; PRAC+ABO configurations; metrics=maximum aggressor activations; safe TRH; slowdown; SRAM overhead; results=Panopticon reaches 1,150 activations at threshold 128; MOAT ATH=64 safe for TRH=99; 0.28% average slowdown; 7 bytes SRAM per bank Interpretation: Accurate per-row counters are insufficient unless queue service, delayed alerts, and reset semantics are included in the security proof. Reusable lesson: Prove the complete mitigation state machine against adversarial scheduling, including backpressure and counter reset. Applicability: DDR5 PRAC/ABO RowHammer mitigation designs. Limits: Security bound depends on timing and threshold assumptions; evaluation is simulation/workload based and must track JEDEC/device implementation details. not_recorded moat securely mitigating rowhammer with per row activation counters 6e5ed0e1# ec8cb6775aebf7ece69a781d98a80f88 3000 canonical-paper-v2-6e5ed0e1 2026-07-18T05:30:01Z 2461239.7291782 S3ResearchAgent Moinuddin Qureshi et al., "MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters", ASPLOS 2025. paper Verification: full_text; confidence=high. Canonical title: MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters Question: Can DDR5 per-row activation counting and ALERT back-off be implemented with provable RowHammer security and low overhead? Context: PRAC+ABO specifies mechanisms, not a secure policy; Panopticon's queue can be manipulated by crafted activation patterns. Method: MOAT uses an eligibility threshold for proactive mitigation, an ALERT threshold for ABO, highest-count row tracking, and safe counter reset around refresh. Evaluation: workloads=SPEC CPU; GAP graph workloads; Jailbreak and performance attacks; baselines=Panopticon; PRAC+ABO configurations; metrics=maximum aggressor activations; safe TRH; slowdown; SRAM overhead; results=Panopticon reaches 1,150 activations at threshold 128; MOAT ATH=64 safe for TRH=99; 0.28% average slowdown; 7 bytes SRAM per bank Interpretation: Accurate per-row counters are insufficient unless queue service, delayed alerts, and reset semantics are included in the security proof. Reusable lesson: Prove the complete mitigation state machine against adversarial scheduling, including backpressure and counter reset. Applicability: DDR5 PRAC/ABO RowHammer mitigation designs. Limits: Security bound depends on timing and threshold assumptions; evaluation is simulation/workload based and must track JEDEC/device implementation details. full_text moat securely mitigating rowhammer with per row activation counters 6e5ed0e1# b9b680c2f5e3d3a0f020cadd35ce7d84 3000 2026-07-18T14:58:44Z 2461240.1241204 S3ResearchAgent verify_8b67e36160d035629073 metadata_only context 보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함. inconclusive 49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 보존 파일 objects/sha256/49/49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 ev_6fbdb1b582084fad da3a92f72518af2d39d3c3fd28ae52c8944445a1f0d770e07df1fc102b6d9c12 moat securely mitigating rowhammer with per row activation counters 6e5ed0e1# dc4e09b4cd5127ab10734b80a7a21dbf 3000 2026-07-18T14:58:45Z 2461240.1241319 S3ResearchAgent verify_ca977fe1bbd51e0083f9 metadata_only context 보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함. inconclusive 49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 보존 파일 objects/sha256/49/49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 verified-content-v1-0106 887bdf4fe623c0a8bf172edefb8af1a9101cb17b1e0875787e8843eed9723767 moat securely mitigating rowhammer with per row activation counters 6e5ed0e1# 194107e5fa192c4c6fa9ee6f1577d5e2 3000 2026-07-18T14:58:45Z 2461240.1241319 S3ResearchAgent verify_ccb37a70fddf9436892a metadata_only context 보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함. inconclusive 49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 보존 파일 objects/sha256/49/49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 canonical-paper-v2-6e5ed0e1 1619aa2704b12ded25cf9cddf8033af49b4c86bfe5d9a5026db0fb0ce770bd11 moat securely mitigating rowhammer with per row activation counters 6e5ed0e1# 49e95222cd860d128d183349bbf68a2f 3000 2026-07-18T14:58:46Z 2461240.1241435 S3ResearchAgent verify_c6d6b4cb15f590e25cc0 metadata_only observation,interpretation,reusable_lesson claim-bearing O/I/R coverage was not established; confidence forced to low inconclusive 49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9; high-confidence adjudication ledger Saved HTML inspected in full; it is a cookie/landing/generic metadata page and contains no claim-bearing text covering O/I/R. canonical-paper-v2-6e5ed0e1 1619aa2704b12ded25cf9cddf8033af49b4c86bfe5d9a5026db0fb0ce770bd11 moat securely mitigating rowhammer with per row activation counters 6e5ed0e1# 281434fdfba91aabf96ec5c1826da782