Linux kernel CVE-2026-46300: local privilege escalation and patch guide

Venus Yazılım6 min read

CVE-2026-46300 in the Linux kernel lets a local user gain root. Affected versions, fixed kernels, and what to do on shared and multi-user servers.

On shared hosting or any multi-user Linux server, a low-privileged user who exploits one kernel bug can take over the whole machine. Check your kernel version today.

Short answer: CVE-2026-46300 is a bug in the Linux kernel’s networking code. When incoming packet fragments are merged, a flag that marks the data as shared is lost, and the IPsec decryption path can then decrypt that data in place instead of copying it first. A local user with low privileges can use this to gain root. Update your distribution’s kernel through its security channel and reboot.

At a glance

Field Detail
CVE CVE-2026-46300
CVSS 7.8 (v3.1), as scored by NVD and Red Hat. Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness type Missing initialization of a variable (CISA KEV wording, CWE-456)
Authentication Local access and a low-privileged account are required. No user interaction.
Active exploitation Listed in the CISA KEV catalog. KEV is used for vulnerabilities with evidence of active exploitation.
CISA KEV added 28 October 2026. Due date for federal agencies: 31 October 2026.
Fixed versions Stable branches: 5.10.257, 5.15.208, 6.1.174, 6.6.141, 6.12.91, 6.18.33, 7.0.10, and 7.1 onward. Distribution packages are listed below.

What happened?

To run faster, the Linux kernel merges several fragments of a network packet into one buffer instead of copying them (skb_try_coalesce()). Some of these fragments can come from the page cache, which is the in-memory copy of files. The kernel marks such fragments as “shared” so that later code does not change them in place.

During the merge, that marker is lost. IPsec’s ESP layer, which encrypts network traffic, sees the buffer as unshared and decrypts it in place, without copying. The data in the page cache can then change. The fix keeps the marker when fragments are moved during the merge.

Ubuntu calls this flaw “Fragnesia” and describes it as a local privilege escalation that could also allow a container escape. Red Hat says a low-privileged local attacker can overwrite sensitive system files and gain root.

Who is affected?

  • According to NVD, Linux kernels from 3.9 onward are affected. Earlier versions are listed as not affected.
  • Stable branches between 3.9 and the fixed releases are affected. The fixed stable releases are 5.10.257, 5.15.208, 6.1.174, 6.6.141, 6.12.91, 6.18.33, and 7.0.10. Version 7.1 and later include the fix.
  • Ubuntu’s supported releases, including 22.04 LTS and 24.04 LTS, are affected. Ubuntu lists 26.10 as not affected.
  • Debian bookworm, trixie, forky, and sid have fixed packages.
  • Red Hat Enterprise Linux 8, 9, and 10, and products built on the RHEL kernel (including OpenShift), are affected.

Why this matters on shared servers

On shared hosting, every account runs on the same kernel. If an attacker compromises a web application and gets a low-privileged shell, for example as the PHP user, this bug can turn that foothold into root, exposing the other accounts and the whole server.

The CISA KEV entry says this flaw can be chained with CVE-2026-109618 and CVE-2026-109619 to plant PHP web shells and run commands as root. For PHP hosting, that is a concrete risk. For the PHP side, see our PHP CVE-2026-109618 and CVE-2026-109619 article.

What should you do?

  1. Check your kernel version.
uname -r
cat /etc/os-release
  1. Install the security update from your distribution.

On Ubuntu and Debian:

sudo apt update && sudo apt full-upgrade

The fixed Ubuntu kernel packages are 6.8.0-124.124 for 24.04 LTS and 5.15.0-181.191 for 22.04 LTS. On Debian, aim for 6.1.190-1 on bookworm and 6.12.115-2 on trixie, or newer.

On RHEL 8, 9, 10, and derivatives:

sudo dnf update kernel

NVD’s Red Hat entries list the fixed kernel for RHEL 10.2 as 6.12.0-211.16.1.el10_2, and for RHEL 8 as 4.18.0-553.125.1.el8_10.

  1. Reboot the server. The new kernel only runs after a reboot.
sudo reboot

After the server is back up, confirm the new version with uname -r.

  1. If you use livepatch, check its status. The sources we reviewed do not say that a live patch closes this CVE, so do not skip the reboot.

  2. If you cannot update right away, apply Red Hat’s temporary mitigation. Red Hat’s advisory RHSB-2026-003 covers this CVE together with others under the “Dirty Frag” name. Its broad mitigation blocks the IPsec modules. Run as root:

printf 'install esp4 /bin/false\ninstall esp6 /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf
rmmod esp4 esp6 2>/dev/null; true

The advisory warns that this breaks IPsec. For environments that need IPsec, it describes a narrower option that disables unprivileged user namespaces with user.max_user_namespaces=0. That can affect rootless containers, sandboxed browsers, and Flatpak. Red Hat still recommends running a current RHEL kernel. The mitigation is not a replacement for the patch.

Have I been hit?

The sources we reviewed do not publish file names or network indicators (IoCs) for this CVE. A clean-looking system is therefore not proof of safety. We suggest these checks:

  • Unusual sessions: last -a | head -n 30 and sudo journalctl --since "7 days ago" -p warning.
  • Unexpected SUID files: sudo find / -xdev -perm -4000 -type f, then compare the output with your package manager’s records.
  • Unexpected PHP files in web directories, especially writable ones. The KEV web shell note makes this check important.
  • Cron jobs and authorized_keys files for every account.

If you suspect a compromise, copy the logs before you rebuild the server. The CISA KEV entry also flags this CVE for forensic triage.

Frequently asked questions

Can this be exploited remotely?

No. NVD and Red Hat both say the attack requires local access. A remote bug, such as a web application flaw, could still give an attacker the first foothold. This CVE would then be the second step. The KEV chaining note points to this risk.

I do not use IPsec. Do I still need to update?

Yes. Red Hat’s broad mitigation is written for systems that do not need IPsec, and it is not a patch.

Does livepatch close this vulnerability?

The sources we reviewed do not say so. The safe route is to install your distribution’s kernel update and reboot.

Sources

If you want help keeping a server patched, planning reboots, or hardening a multi-user environment, take a look at our server management service.

More notes

  1. 4 min read

    Google Brotli CVE-2026-111497: memory overflow in Node.js and Brotli libraries

    A memory overflow in the Brotli decoder (CVE-2026-111497) can lead to code execution without logging in. Update Node.js and Brotli.

  2. 5 min read

    Cisco ASA and FTD CVE-2026-76418: SSL VPN reload flaw and fixed releases

    Unauthenticated attackers can reload Cisco ASA and FTD devices through SSL VPN when secondary authentication is set. It is being exploited. Check and upgrade.

Let’s reserve a slot in the rack.

Describe your project in a few steps and we’ll prepare a written proposal with scope, timeline and an infrastructure plan.

Request a quoteor write directly: email address