<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Memory-Safety on Protocol Notes</title><link>https://syycorax.xyz/tags/memory-safety/</link><description>Recent content in Memory-Safety on Protocol Notes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://syycorax.xyz/tags/memory-safety/index.xml" rel="self" type="application/rss+xml"/><item><title>Stack Smashing to ROP: What a Return Address Is Worth</title><link>https://syycorax.xyz/posts/stack-smashing-to-rop/</link><pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate><guid>https://syycorax.xyz/posts/stack-smashing-to-rop/</guid><description>How a bounds check failure becomes control of the instruction pointer, what each mitigation blocks, and why ROP still works on a stack that cannot execute.</description></item></channel></rss>