The responsible disclosure embargo for Dirty Frag was broken by a third party before any distribution had prepared a patched kernel. As of the publication of this document, no distribution-level patch exists for either CVE-2026-43284 or CVE-2026-43500. Until your distribution releases a backported fix, you must take manual action to remove the vulnerable kernel modules and clear any page cache that may already have been modified.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/V4bel/dirtyfrag/llms.txt
Use this file to discover all available pages before exploring further.
Primary mitigation
Run the following single command as root to blacklist the three vulnerable modules, unload them if they are currently loaded, and drop the page cache:- Blacklists
esp4,esp6, andrxrpcby writing install rules to/etc/modprobe.d/dirtyfrag.conf. After this,modprobewill refuse to load any of the three modules. - Unloads the modules with
rmmodif they are currently present in the running kernel. Errors (for example, if a module was not loaded) are suppressed via2>/dev/null. - Drops the page cache with
echo 3 > /proc/sys/vm/drop_caches, clearing any contaminated pages already present in RAM.
Step-by-step procedure
Run the blacklist command
Execute the primary mitigation command above as root. The command is intentionally written as a single
sh -c invocation so you can paste it into any shell without line-continuation issues.Verify the modules are gone
Confirm that none of the three modules remain loaded:The command should produce no output. If any module still appears, the
rmmod step may have failed because another kernel module depends on it. Identify and remove the dependent module first, then re-run rmmod.Clearing the page cache after running the exploit
If you ran the exploit for testing purposes (on an authorized system), clear the contaminated page cache before continuing to use the system:Current patch status
CVE-2026-43284 (xfrm-ESP): The fix is merged in mainline at commit
f4c50a4034e6 (2026-05-08). The patch sets the SKBFL_SHARED_FRAG flag on page frags that enter the kernel via splice in the IPv4/IPv6 datagram append paths, and checks this flag in the skip_cow branch of esp_input / esp6_input so that externally pinned pages are always routed through skb_cow_data(). Wait for your distribution to backport this commit.CVE-2026-43500 (RxRPC): No upstream patch exists yet. The submitted patch adds || skb->data_len to the guard condition in call_event.c and conn_event.c, ensuring that non-linear skbs (including those with spliced frags) are isolated via skb_copy() before in-place decryption. Monitor the netdev mailing list and your distribution’s advisories for when this is merged and backported.