CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-09
HIGHCVE-2026-43284 +1updatedNATOB2vulnerability

CVE-2026-43284 / CVE-2026-43500 Linux Dirty Frag: deterministic page-cache write to root through xfrm-ESP and RxRPC, public exploit, fixes released

Dirty Frag: two kernel page-cache write flaws give local root; Microsoft saw su escalation that may be it or Copy Fail

Defender actions

  • Apply the distribution kernel update for CVE-2026-43284 and CVE-2026-43500, and confirm the fix for CVE-2026-46300 is installed too.

Analysis

Researcher Hyunwoo Kim (V4bel) published "Dirty Frag" on 2026-05-07, after the embargo had been broken by external factors and before patches or CVE ids existed (V4bel, 2026-05-07). It is two page-cache write flaws: CVE-2026-43284 in the xfrm-ESP (IPsec) receive path, in the kernel since 2017 and fixed in mainline commit f4c50a4034e6, and CVE-2026-43500 in RxRPC, in the kernel since 2023 and fixed in mainline commit aa54b1d27fe0 (V4bel, 2026-05-07). In both, a page-cache page planted with splice() sits in a fragment of a network buffer and the receiving code decrypts it in place, writing into the cached copy of a file: the ESP variant stores 4 attacker-chosen bytes per trigger into a setuid binary such as su, and the RxRPC variant stores 8 bytes whose value the attacker brute-forces through the session key, aimed at /etc/passwd; the result is deterministic root without a race window (V4bel write-up, 2026-05-07). The ESP variant needs the privilege to create a user namespace, which Ubuntu sometimes blocks through AppArmor; the RxRPC variant needs no namespace but depends on the rxrpc module, which most distributions do not ship and Ubuntu loads by default (V4bel, 2026-05-07). The kernel.org CNA scores CVE-2026-43284 CVSS 8.8, and NVD and CISA score CVE-2026-43500 7.8 (Ubuntu, 2026-05-08). Microsoft reports limited in-the-wild privilege escalation involving su that "may be indicative of techniques associated with either" Dirty Frag or Copy Fail: an SSH session ran an ELF binary that escalated through su, then edited a GLPI LDAP authentication file and deleted and read web session files (Microsoft Security Blog, 2026-05-08). Copy Fail is the earlier CVE-2026-31431 (Microsoft Security Blog, 2026-05-08).

The researcher tested the exploit on Ubuntu 24.04.4, RHEL 10.1, openSUSE Tumbleweed, CentOS Stream 10, AlmaLinux 10 and Fedora 44 (V4bel, 2026-05-07). Ubuntu publishes fixed kernels for every supported release from 18.04 to 26.04 (Ubuntu, 2026-05-08), and Red Hat states that fixes are released for all affected products and that CVE-2026-43500 does not affect Red Hat products (Red Hat RHSB-2026-003). Where a fix cannot be applied, NCSC-CH advises blocking or removing the esp4, esp6 and rxrpc modules (NCSC-CH advisory 12547, 2026-05-08), which affects IPsec and AFS where they are in use (Ubuntu, 2026-05-08); on RHEL, user.max_user_namespaces=0 blocks the ESP path (Red Hat RHSB-2026-003).

Updates4

Update

Microsoft's Defender Security Research Team reported on 2026-05-08 "limited in-the-wild activity where privilege escalation involving ‘su’ is observed, and which may be indicative of techniques associated with either “Dirty Frag” or “Copy Fail”": an external connection gained SSH access, spawned a shell and ran an ELF binary that immediately escalated through su (Microsoft Security Blog, 2026-05-08). Microsoft does not say which flaw the binary used.

Red Hat's bulletin RHSB-2026-003 lists the Dirty Frag CVEs, states that CVE-2026-43500 does not affect Red Hat products, and gives user.max_user_namespaces=0 as a targeted mitigation alongside blocking the ESP modules (Red Hat RHSB-2026-003). NCSC.ch's Security Hub post 12547 of 2026-05-08 noted a public proof of concept and advised temporarily blacklisting esp4, esp6 and rxrpc (NCSC-CH advisory 12547, 2026-05-08), and Belgium's CCB issued a parallel advisory (CCB Belgium, 2026-05-08).

The mainline fixes are f4c50a4034e6 for the ESP flaw and aa54b1d27fe0 for the RxRPC flaw (V4bel, 2026-05-07). Microsoft warns that modifications made before mitigation may persist in cached file content even after the vulnerable modules are disabled (Microsoft Security Blog, 2026-05-08). On Ubuntu systems where AppArmor blocks unprivileged user namespaces, the ESP path cannot be triggered, while the RxRPC path needs no namespace (V4bel, 2026-05-07). Blocking rxrpc breaks AFS and other RxRPC uses, so for those hosts the kernel update is the fix (Ubuntu, 2026-05-08).

Update

A related flaw, CVE-2026-46300 ("Fragnesia"), reopens this vulnerability's underlying page-cache-write primitive even on hosts already patched against CVE-2026-43284: a bug from 2013 in the code that merges packet fragments drops the marker that flags a fragment as page-cache-backed, which the original xfrm-ESP fix depends on to decide whether it is safe to decrypt in place (Aikido Security). Red Hat's own security bulletin groups all three CVEs under the collective "Dirty Frag" name, notes that the family is similar enough to the earlier Copy Fail flaw to be called "Copy Fail 2", and confirms CVE-2026-46300 affects supported Red Hat Enterprise Linux kernels; administrators who patched only against CVE-2026-43284/CVE-2026-43500 should verify the CVE-2026-46300 fix is applied too (Red Hat RHSB-2026-003). Public proof-of-concept exploits for this family now target Kubernetes specifically, extending the exposure to container-shared-kernel environments beyond the bare-metal/VM case originally described (Aikido Security).

Correction

Microsoft's observation of su-based escalation "may be indicative of techniques associated with either" Dirty Frag or Copy Fail (Microsoft Security Blog, 2026-05-08), so exploitation of these two CVEs is not confirmed. The flaws work by decrypting a splice()-planted page-cache page in place, not through DMA remapping (V4bel write-up, 2026-05-07); mainline fixed the ESP flaw in f4c50a4034e6 and the RxRPC flaw in aa54b1d27fe0, and distribution kernels are available (V4bel, 2026-05-07) (Ubuntu, 2026-05-08). Red Hat says CVE-2026-43500 does not affect its products and gives user.max_user_namespaces=0 as its targeted mitigation (Red Hat RHSB-2026-003). The write modifies the page cache in RAM (V4bel write-up, 2026-05-07) while the file on disk never changes (Aikido Security, 2026-09-04), so a file-write watch does not fire. The ESP variant stores 4 attacker-chosen bytes per trigger into a setuid binary such as su; the RxRPC variant stores 8 bytes whose value the attacker brute-forces through the session key, aimed at /etc/passwd (V4bel write-up, 2026-05-07).

Improvement

FIRST's EPSS probability was 0.0262 for CVE-2026-43500 and 0.9419 for CVE-2026-43284 on 2026-10-20 (FIRST.org EPSS API, 2026-10-20); on 2026-09-04 the two scores were 0.9286 and 0.9324 (FIRST.org EPSS API, 2026-09-04). Microsoft's report of 2026-05-08 is by its Defender Security Research Team (Microsoft Security Blog, 2026-05-08).

Sources10

Revision history

  1. Published 2026-05-09-migrated
  2. Update 2026-05-11-migrated

    Dirty Frag Linux LPE now confirmed exploited in the wild; Microsoft Threat Intelligence reports "limited in-the-wild activity" involving su privilege escalation after SSH initial access (Microsoft Security Blog, 2026-05-08). Red Hat published RHSB-2026-003 with backports rolling out (Red Hat, updated 2026-05-09); NCSC.ch issued a Swiss federal advisory (NCSC-CH Security Hub post 12547, 2026-05-08).

    Changed: cves evidence regions sources body

  3. Update 2026-09-05T0409Z-intel

    A related follow-on flaw, CVE-2026-46300 ("Fragnesia", tracked in its own entry), reopens this vulnerability's page-cache-write primitive on hosts patched only against CVE-2026-43284: a 13-year-old bug in the kernel's skb-coalescing code drops the shared-fragment marker the original fix relies on. Public Kubernetes-context proof-of-concept exploits now exist, and Red Hat confirms RHEL kernels need the CVE-2026-46300 fix too. EPSS scores (FIRST.org, 2026-09-04) are now populated: 0.9324 for CVE-2026-43284 and 0.9286 for CVE-2026-43500.

    Changed: updated_at cves entities classification techniques sources actions sourcing_note body

  4. Correction 2026-10-11T1307Z-audit

    Exploitation of Dirty Frag is not confirmed: Microsoft's observation may be Dirty Frag or Copy Fail, and Microsoft does not report exfiltration, so the exploited status is removed. The root cause is in-place decryption of a spliced page-cache page, not DMA remapping; only the ESP variant needs a user namespace; the tested distributions and Ubuntu releases were wrong; Red Hat's bulletin does not cover CVE-2026-43500, which does not affect Red Hat, and its targeted sysctl is user.max_user_namespaces; a file-write watch cannot see the page-cache write; and Microsoft does not mention AIDE, IMA or auditd. The summary's pending-patch state is superseded: both mainline fixes and distribution kernels are released. CVSS for CVE-2026-43284 is the CNA's 8.8, the duplicate Red Hat source and self-quoted evidence are removed, and the earlier sections are corrected in place. The two flaws' write primitives are told apart (4 chosen bytes into a setuid binary for ESP, 8 brute-forced bytes into /etc/passwd for RxRPC), the Copy Fail CVE is cited to Microsoft, the on-disk clause to Aikido, the AFS effect to Ubuntu, the 2013 bug is described without a function name the sources do not give, the NCSC-CH citation points at the public hub post, and the action is cut to the patch task. The main analysis gains Exposure and takeaway lines.

    Changed: title headline summary event_date tags cves affected_products sources evidence sourcing_note body actions

  5. Improvement 2026-10-21T1149Z-audit

    FIRST's EPSS scores are refreshed to 2026-10-20: CVE-2026-43500 has fallen to 0.0262 from 0.9286 on 2026-09-04, while CVE-2026-43284 stands at 0.9419. Microsoft's report is credited to its Defender Security Research Team, which wrote it. Red Hat's 'Copy Fail 2' nickname is dropped from the main analysis, and the separate Copy Fail entry (CVE-2026-31431) is linked.

    Changed: cves sources sourcing_note body headline references

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.