Skip to main content
Mallory
Back to intelligence
proof-of-concept-releasewidely-deployed-product-advisoryendpoint-software-vulnerabilitydetection-content-update

Linux Dirty Frag and Copy Fail Flaws Spur Calls for Kernel Killswitch

Updated 9d agoFirst seen May 11, 20266 sources

Linux developers and government defenders are responding to newly disclosed local privilege-escalation flaws Dirty Frag and Copy Fail, which can let unprivileged users gain root on affected systems. Dirty Frag combines CVE-2026-43284 and CVE-2026-43500 in Linux networking components tied to IPSec ESP and RxRPC, while Copy Fail (CVE-2026-31431) is a separate AF_ALG cryptographic socket flaw. Researchers said the bugs had existed for years, proof-of-concept exploit material is public, and affected environments include major enterprise distributions such as RHEL, Ubuntu, Fedora, CentOS Stream, AlmaLinux, and OpenShift deployments.

The Canadian Centre for Cyber Security warned that Dirty Frag could be chained with remote code execution for more severe compromise and advised organizations to identify exposed systems, disable vulnerable modules where possible, regenerate initramfs, restrict access, reduce privileges, and monitor logs until vendor patches arrive. In parallel, Linux kernel maintainer Sasha Levin proposed an emergency runtime Killswitch mechanism that would let administrators temporarily disable vulnerable kernel functions until reboot, aiming to reduce exposure when public disclosure outpaces patch distribution; the proposal remains under review and has not yet been merged.

Share:
Linux Dirty Frag and Copy Fail Flaws Spur Calls for Kernel Killswitch
Stay ahead

Get ahead of threats like this

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.

EVENT TIMELINE

How this story unfolded

7 events from the most recent confirmed update back to the earliest known activity.

7 EVENTS
May 11, 202610d ago

Linux developers propose Killswitch runtime mitigation

By 2026-05-11, Linux kernel developers were reviewing Sasha Levin's proposed Killswitch mechanism, intended to let administrators disable vulnerable kernel functions at runtime as a stop-gap defense between public disclosure and patch deployment.

May 8, 202613d ago

fsnotify maintainer denies takeover and cites governance dispute

During the fsnotify controversy, maintainer Martin Tournoij said the removed accounts were not active maintainers and that access was revoked over rushed merges and an unauthorized sponsorship-file change, framing the incident as a maintainer dispute rather than a compromise.

fsnotify maintainer removals trigger supply-chain takeover concerns

By 2026-05-08, contributor access changes in the fsnotify GitHub organization had sparked fears of a possible supply-chain compromise after Yasuhiro Matsumoto said he had been removed from the project and recent releases came under scrutiny.

Canadian Centre for Cyber Security issues Dirty Frag alert

On 2026-05-08, the Canadian Centre for Cyber Security published Alert AL26-011 warning that CVE-2026-43284 and CVE-2026-43500 could be chained for root compromise, noting public proof-of-concept exploits and the lack of a universal fix across stable kernels.

May 7, 202614d ago

Researcher Hyunwoo Kim publicly discloses Dirty Frag flaws

On 2026-05-07, researcher Hyunwoo Kim publicly disclosed the Linux kernel vulnerabilities CVE-2026-43284 and CVE-2026-43500, collectively referred to as Dirty Frag, showing they could be chained for local privilege escalation to root.

Public upstream patch accelerates Dirty Frag exploit development

Before Dirty Frag was publicly disclosed, an upstream Linux patch became public and enabled another researcher to rapidly develop an exploit, contributing to the accelerated disclosure timeline described by kernel developers.

Apr 29, 202622d ago

Theori publicly discloses Copy Fail privilege-escalation flaw

On 2026-04-29, Theori publicly disclosed Copy Fail (CVE-2026-31431), a nine-year-old AF_ALG Linux kernel flaw that enables reliable local root escalation by allowing controlled writes into the kernel page cache of readable files.

The operational view lives in Mallory

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t — which of your assets are affected, which threat actors are using it right now, which detections to deploy, and what to do next.
Exposure mapping

Map indicators from this story to your assets and identify affected systems in minutes.

Threat actor evidence

Every observed campaign, victim, and pivot linked to actors named in this story.

Associated malware

Malware, exploits, and IOCs connected to the activity described here.

Detection signatures

YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.

Scheduled alerts

Get matching new stories delivered to your team as they break — not the next morning.

AI threads

Ask questions about this story and take action on the answers.