<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Kernel Cardistry Blog</title>
		<link>https://kernelcardistry.com/</link>
		<description>Recent content on Kernel Cardistry Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<atom:link href="https://kernelcardistry.com/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>memfd_secret() and the illusion of secret memory</title>
				<link>https://kernelcardistry.com/posts/secretmem/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://kernelcardistry.com/posts/secretmem/</guid>
				<description>&lt;p&gt;Introduced in Linux 5.14, &lt;a href=&#34;https://man7.org/linux/man-pages/man2/memfd_secret.2.html&#34;&gt;&lt;code&gt;memfd_secret&lt;/code&gt;&lt;/a&gt; is a system call that allows a userspace process to create memory regions inaccessible to anything outside of it &amp;ndash; including the kernel itself. According to the man page:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;code&gt;memfd_secret()&lt;/code&gt; creates an anonymous RAM-based file and returns a file descriptor that refers to it. The memory areas backing the file created with &lt;code&gt;memfd_secret(2)&lt;/code&gt; are&#xA;visible only to the processes that have access to the file&#xA;descriptor.  The memory region is removed from the kernel page&#xA;tables and only the page tables of the processes holding the file&#xA;descriptor map the corresponding physical memory.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
