---
id: "CVE-2026-53362"
kind: "vulnerability"
aliases: ["CVE-2026-53362"]
title: "In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged\u2026"
severity: "high"
cvss: 7.8
epss: null
exploited: true
status: "open"
category: "infrastructure"
products: [{"name": "linux kernel", "fixed": ["6.1.177"], "affected": ">= 6.0, < 6.1.177", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.6.144"], "affected": ">= 6.2, < 6.6.144", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.12.95"], "affected": ">= 6.7, < 6.12.95", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.18.38"], "affected": ">= 6.13, < 6.18.38", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["7.1.3"], "affected": ">= 6.19, < 7.1.3", "ecosystem": "vendor"}, {"name": "siemens simatic s7-1500 tm mfp firmware", "fixed": [], "affected": "", "ecosystem": "vendor"}, {"name": "Linux Kernel", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["exploited", "infrastructure", "kubernetes", "linux", "red-hat", "self-hosted", "suse"]
not_affected_if: ["kernel-patched", "managed-hosting"]
published_at: "2026-07-04T12:17:02+00:00"
first_seen_at: "2026-10-23T19:11:51+00:00"
updated_at: "2026-10-24T00:09:50+00:00"
sources: [{"source": "kev", "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-53362", "first_seen_at": "2026-10-23T19:11:51+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53362", "first_seen_at": "2026-10-23T23:44:52+00:00"}]
---

# In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged…

The Linux kernel has an unspecified flaw in its IPv6 networking code that allows privilege escalation. CISA lists it as actively exploited, so an attacker with local code execution can gain root.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:linux kernel affected >= 6.0, < 6.1.177 fixed 6.1.177
- vendor:linux kernel affected >= 6.2, < 6.6.144 fixed 6.6.144
- vendor:linux kernel affected >= 6.7, < 6.12.95 fixed 6.12.95
- vendor:linux kernel affected >= 6.13, < 6.18.38 fixed 6.18.38
- vendor:linux kernel affected >= 6.19, < 7.1.3 fixed 7.1.3
- vendor:siemens simatic s7-1500 tm mfp firmware affected ? fixed ?
- vendor:Linux Kernel affected ? fixed ?

## How to check

uname -r to see the running kernel version, then compare it against the fixed kernel builds from your distribution's security advisory for CVE-2026-53362.

## Fix

Install the kernel update from your distribution vendor (SUSE, Red Hat, or others named in the advisory) and reboot.

## Timeline

- 2026-10-23T19:11:51+00:00 kev https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-53362
- 2026-10-23T23:44:52+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-53362

## From the sources

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

ipv6: account for fraggap on the paged allocation path

In __ip6_append_data(), when the paged-allocation branch is taken
(MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are
computed as

	alloclen = fragheaderlen + transhdrlen;
	pagedlen = datalen - transhdrlen;

datalen already includes fraggap (datalen = length + fraggap). When
fraggap is non-zero, this is not the first skb and transhdrlen is zero.
The fraggap bytes carried over from the previous skb are copied just past
the fragment headers in the new skb's linear area. The linear area is
therefore undersized by fraggap bytes while pagedlen is overstated by the
same amount, and the copy writes past skb->end into the trailing
skb_shared_info.

An unprivileged user can trigger this via a UDPv6 socket using
MSG_MORE together with MSG_SPLICE_PAGES.

The bad accounting was introduced by commit 773ba4fe9104 ("ipv6:
avoid partial copy for zc"). Before commit ce650a166335 ("udp6: Fix
__ip6_append_data()'s handling of MSG_SPLICE_PAGES"), the negative
copy value caused -EINVAL to be returned. That later commit allowed
MSG_SPLICE_PAGES to proceed in this case, making the corruption
triggerable.

The non-paged branch sets alloclen to fraglen, which already accounts
for fraggap because datalen does. Bring the paged branch in line by
adding fraggap to alloclen and subtracting it from pagedlen.

After this adjustment, copy no longer collapses to -fraggap on the
paged path, so remove the stale comment describing that old arithmetic.
Since a negative copy is no longer expected for a valid MSG_SPLICE_PAGES
case, remove the MSG_SPLICE_PAGES exception from the negative copy check.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_