<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kernel-Security on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/kernel-security/</link><description>Recent content in Kernel-Security on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 17 Jun 2026 12:55:58 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/kernel-security/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenBSD Let Attackers Log In With an Empty Password for 27 Years</title><link>https://hackingpassion.com/openbsd-pap-empty-password-bypass/</link><pubDate>Wed, 17 Jun 2026 12:55:58 +0200</pubDate><guid>https://hackingpassion.com/openbsd-pap-empty-password-bypass/</guid><description>&lt;p>A 27-year-old flaw in &lt;strong>OpenBSD&lt;/strong> let attackers bypass its &lt;strong>PPP&lt;/strong> login with nothing more than an empty username and an empty password.
Hand a vulnerable system a blank name and a blank password, and its own login check treated that as a perfect match and let the connection in.&lt;/p>
&lt;p>The problem sits in the part of OpenBSD that handles &lt;strong>PPP&lt;/strong>, the protocol behind many DSL and fiber connections, usually carried through &lt;strong>PPPoE&lt;/strong>. When two machines set up that kind of link, one side can ask the other to prove who it is. One of the older ways to do that is &lt;strong>PAP&lt;/strong>, the Password Authentication Protocol. One machine sends a name and a password, the other checks them against what it has stored, and if they match the link comes up.&lt;/p></description></item><item><title>ssh-keysign-pwn Lets Any Linux User Steal SSH Keys and Password Hashes Without Root</title><link>https://hackingpassion.com/ssh-keysign-pwn-cve-2026-46333/</link><pubDate>Sat, 16 May 2026 11:50:16 +0200</pubDate><guid>https://hackingpassion.com/ssh-keysign-pwn-cve-2026-46333/</guid><description>&lt;p>&lt;strong>ssh-keysign-pwn&lt;/strong> is a newly disclosed Linux kernel vulnerability that gives any unprivileged local user direct access to the SSH host private keys of a server and every password hash stored on the system. It was reported on &lt;strong>May 14, 2026&lt;/strong>, and a working exploit was on GitHub within hours of the patch landing.&lt;/p>
&lt;p>The bug lives in a piece of kernel code called &lt;code>__ptrace_may_access()&lt;/code>. This is the security check the kernel runs every time one program wants to look inside another program: reading its memory, accessing its open files. The kernel runs this check and asks: is this target process marked as safe to inspect, and does the caller have the right to do this? If either answer is no, access is denied. That is how it is supposed to work.&lt;/p></description></item><item><title>Dirty Frag Gives Root Access on Every Major Linux Distribution</title><link>https://hackingpassion.com/dirty-frag-linux-root/</link><pubDate>Fri, 08 May 2026 10:24:54 +0200</pubDate><guid>https://hackingpassion.com/dirty-frag-linux-root/</guid><description>&lt;p>A new Linux zero-day called &lt;strong>Dirty Frag&lt;/strong> gives any local user full root access on every major Linux distribution, and right now no distribution has a patched kernel available. The researcher planned to give distributions until May 12 to prepare. Someone leaked the exploit five days early, and it went public before a single distribution had a fix ready.&lt;/p>
&lt;p>&lt;strong>Hyunwoo Kim&lt;/strong> (@v4bel) found both vulnerabilities and quietly reported them to the Linux kernel security team at the end of April, including working exploits and patches. The plan was to give Linux distributions until May 12 to prepare fixes before anything went public. On May 7, he told the group of distribution maintainers about it and set that five-day hold in motion. That same day, someone else published the exploit online. The agreement was clear: if that happened, everything would go public immediately. Kim released the full details within hours. Two CVEs have since been assigned: &lt;strong>CVE-2026-43284&lt;/strong> for the IPsec variant, which now has a patch in the kernel mainline, and &lt;strong>CVE-2026-43500&lt;/strong> for the RxRPC variant, which has no patch anywhere yet. How the exploit got out early is still unknown. The patch for the IPsec bug had been sitting on a public kernel mailing list since April 30, so someone paying close attention to kernel development could have spotted it there. Or someone inside the distribution group leaked it. Nobody knows.&lt;/p></description></item><item><title>Copy Fail CVE-2026-31431: Nine Years of Root Access Hidden in the Linux Kernel</title><link>https://hackingpassion.com/copy-fail-linux-kernel-cve-2026-31431/</link><pubDate>Thu, 30 Apr 2026 13:13:08 +0200</pubDate><guid>https://hackingpassion.com/copy-fail-linux-kernel-cve-2026-31431/</guid><description>&lt;p>Since 2017, every major Linux distribution has been shipping a flaw that hands root access to any local user. The exploit is a &lt;strong>732-byte Python script&lt;/strong> that uses only what comes built into Python by default. It works on &lt;strong>Ubuntu, Amazon Linux, RHEL, and SUSE&lt;/strong> without a single modification, leaves nothing on disk, and bypasses almost every file integrity monitoring tool in existence, because the file it corrupts is never actually written to.&lt;/p></description></item></channel></rss>