CVE-2026-46300: net: skbuff: preserve shared-frag marker during coalescing

Published May 13, 2026
·
Updated

Fragnesia is a universal Linux local privilege escalation exploit, discovered by William Bowling with the V12 team. Fragnesia is a member of the Dirty Frag vulnerability class. This is a separate bug in the ESP/XFRM from dirtyfrag which has received its own patch. However, it is in the same surface and the mitigation is the same as for dirtyfrag.

It abuses a logic bug in the Linux XFRM ESP-in-TCP subsystem to achieve arbitrary byte writes into the kernel page cache of read-only files, without requiring any race condition.

The technique extends the page-cache write bug class that includes Dirty Pipe: when a TCP socket transitions to espintcp ULP mode after data has already been spliced from a file into the receive queue, the kernel processes the queued file pages as ESP ciphertext. The AES-GCM keystream byte at counter block position 2, byte 0 is XORed directly into the cached file page. By selecting the IV nonce to produce a desired keystream byte, any target byte in the file can be set to any value — one byte per trigger invocation.

The exploit builds a 256-entry lookup table mapping each possible keystream byte to its corresponding nonce, then iterates over a payload, firing the splice/ULP race for each byte that needs changing. It writes a small position-independent ELF stub (setresuid/setresgid/execve /bin/sh) over the first 192 bytes of /usr/bin/su in the page cache, then calls execve("/usr/bin/su") to obtain a root shell. The page cache modification is not backed to disk; the on-disk binary is untouched.

Other sources

In the Linux kernel, the following vulnerability has been resolved:

net: skbuff: preserve shared-frag marker during coalescing

skbtrycoalesce() can attach paged frags from @from to @to. If @from has SKBFLSHAREDFRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost.

That breaks the invariant relied on by later in-place writers. In particular, ESP input checks skbhassharedfrag() before deciding whether an uncloned nonlinear skb can skip skbcowdata(). If TCP receive coalescing has moved shared frags into an unmarked skb, ESP can see skbhassharedfrag() as false and decrypt in place over page-cache backed frags.

Propagate SKBFLSHAREDFRAG when skbtrycoalesce() transfers paged frags. The tailroom copy path does not need the marker because it copies bytes into @to's linear data rather than transferring frag descriptors.

NVD

Affected Software

15 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=3.9<=5.10.257
Linux Linux kernel>=5.11<5.15.208
Linux Linux kernel>=5.16<6.1.174
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
debian/linux<=5.10.223-1, <=6.1.170-3, <=6.12.86-1
5.10.257-16.1.174-16.12.90-27.0.12-2
debian/linux-6.1
6.1.174-1~deb11u1
Microsoft azl3 kernel 6.6.139.1-1<6.6.141.1-1
6.6.141.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.257-1Fixed in 6.1.174-1Fixed in 6.12.90-2Fixed in 7.0.12-2
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.174-1~deb11u1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.141.1-1
  4. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch net: skbuff: preserve shared-frag marker during coalescing

Event History

May 13, 2026
Data Sourced
via Red Hat·01:40 PM
DescriptionSeverityAffected Software
May 14, 2026
News Published
via BleepingComputer·07:30 AM
News Published
via BleepingComputer·07:31 AM
News Published
via BleepingComputer·07:34 AM
May 23, 2026
CVE Published
via MITRE·11:44 AM
Data Sourced
via MITRE·11:44 AM
DescriptionSeverity
Data Sourced
via NVD·12:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 27, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
May 29, 2026
Exploit Published
via ExploitDB·12:00 AM
Known Exploited
11:05 AM
Jun 18, 2026
Data Sourced
via Ubuntu·10:22 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·10:23 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-46300?

The severity of CVE-2026-46300 is rated as high with a score of 7.

2

What systems are affected by CVE-2026-46300?

CVE-2026-46300 affects the Linux kernel.

3

How do I fix CVE-2026-46300?

To fix CVE-2026-46300, apply the latest security patches provided for the Linux kernel.

4

What type of vulnerability is CVE-2026-46300?

CVE-2026-46300 is categorized as a race condition vulnerability.

5

What is the potential impact of CVE-2026-46300?

The potential impact of CVE-2026-46300 is local privilege escalation to root privileges.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203