-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
7 changed files
with
12 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
<?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>Blogs on s4ch</title><link>https://s4ch.github.io/blog/</link><description>Recent content in Blogs on s4ch</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 15 Sep 2024 06:30:05 +0000</lastBuildDate><atom:link href="https://s4ch.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Novel approach to tackle UAF Bugs in the Linux Kernel</title><link>https://s4ch.github.io/blog/bucket-allocators/</link><pubDate>Sun, 15 Sep 2024 06:30:05 +0000</pubDate><guid>https://s4ch.github.io/blog/bucket-allocators/</guid><description><p>Hi, kernel and sec enthusiasts! It&rsquo;s been a while since my last post(2022), but I&rsquo;ve got something juicy for you today. We&rsquo;re going to look at a fascinating new proposal for beefing up the Linux kernel&rsquo;s defenses against those pesky use-after-free (UAF) vulnerabilities. Grab your favorite beverage or drink(Try Amul Kool once, Thank me later), because we&rsquo;re about to get our hands dirty with some kernel internals!</p> | ||
<?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>Blogs on s4ch</title><link>https://s4ch.github.io/blog/</link><description>Recent content in Blogs on s4ch</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 15 Sep 2024 06:30:05 +0000</lastBuildDate><atom:link href="https://s4ch.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Novel approach to tackle UAF Bugs in the Linux Kernel</title><link>https://s4ch.github.io/blog/bucket-allocators/</link><pubDate>Sun, 15 Sep 2024 06:30:05 +0000</pubDate><guid>https://s4ch.github.io/blog/bucket-allocators/</guid><description><p>Hi, kernel and sec enthusiasts! It&rsquo;s been a while since my last post(2022), but I&rsquo;ve got something juicy for you today. We are going to dive into an exciting new proposal that aims to bolster the Linux kernel&rsquo;s defenses against those persistent use-after-free (UAF) vulnerabilities. Grab your favorite beverage or drink(Try Amul Kool once, Thank me later), because we&rsquo;re about to get our hands dirty with some kernel internals!</p> | ||
<h2 id="the-persistent-threat-of-uaf-vulnerabilities">The Persistent Threat of UAF Vulnerabilities</h2> | ||
<p>If you&rsquo;ve been in the low-level security for a while, you&rsquo;re probably sick of hearing about UAF vulnerabilities. But for those who need a refresher, UAFs occur when a program continues to use a pointer to memory after it&rsquo;s been freed. This can lead to all sorts of fun exploitation scenarios, especially in kernel-land where the stakes are highest.</p></description></item></channel></rss> |
Oops, something went wrong.