<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Btw, there&#x27;s _no_ way we&#x27;re done here with #DirtyFrag and #CopyFail.]]></title><description><![CDATA[<p>Btw, there's _no_ way we're done here with <a href="https://mstdn.social/tags/DirtyFrag" rel="tag">#<span>DirtyFrag</span></a> and <a href="https://mstdn.social/tags/CopyFail" rel="tag">#<span>CopyFail</span></a>.  Everybody is aiming their LLMs at this attack path through the page cache now, and there's bound to be other ways.</p><p>Be ready to rinse and repeat a few more times before the dust settles, so I guess keep an even closer eye on linux kernel commits for a while.</p><p>(And no, I don't know how this will be sustainable.)</p>]]></description><link>https://board.circlewithadot.net/topic/1e957641-0f4f-439a-b755-ab1cf17a8130/btw-there-s-_no_-way-we-re-done-here-with-dirtyfrag-and-copyfail.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 07:01:57 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/1e957641-0f4f-439a-b755-ab1cf17a8130.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 08 May 2026 20:27:41 GMT</pubDate><ttl>60</ttl></channel></rss>