CVE-2026-53362
published 2026-07-04CVE-2026-53362: 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…
PriorityP340high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.27%
18.3th percentile
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.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 14200d435af9a9eeb444f529fc2f689a236b7962 | 14200d435af9a9eeb444f529fc2f689a236b7962 |
| linux | linux | >= 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 65fb14cbebb0cd0eff903a22d33537ddc8b95769 | 65fb14cbebb0cd0eff903a22d33537ddc8b95769 |
| linux | linux | >= 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 46f201f8b4c39633a1fa3dc12459f506d470993d | 46f201f8b4c39633a1fa3dc12459f506d470993d |
| linux | linux | >= 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 6374fb9edf72c67a118a2c214a0dddd04c921e0a | 6374fb9edf72c67a118a2c214a0dddd04c921e0a |
| linux | linux | >= 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < e9eacf19281ea2498b36291b56c9606118c2d74e | e9eacf19281ea2498b36291b56c9606118c2d74e |
| linux | linux | >= 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 736b380e28d0480c7bc3e022f1950f31fe53a7c5 | 736b380e28d0480c7bc3e022f1950f31fe53a7c5 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 6.0 < 6.1.177 | 6.1.177 |
| linux | linux_kernel | >= 6.13 < 6.18.38 | 6.18.38 |
| linux | linux_kernel | >= 6.19 < 7.1.3 | 7.1.3 |
| linux | linux_kernel | >= 6.2 < 6.6.144 | 6.6.144 |
| linux | linux_kernel | >= 6.7 < 6.12.95 | 6.12.95 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 7.1.2 ipv6 __ip6_append_data end allocation of resources (EUVD-2026-41669)
vuldb·2026-07-04
CVE-2026-53362 [CRITICAL] Linux Kernel up to 7.1.2 ipv6 __ip6_append_data end allocation of resources (EUVD-2026-41669)
A vulnerability has been found in Linux Kernel up to 6.1.176/6.6.143/6.12.94/6.18.37/7.1.2 and classified as critical. This affects the function __ip6_append_data of the component ipv6. Performing a manipulation of the argument end results in allocation of resources.
This vulnerability was named CVE-2026-53362. The attack needs to be approached within the local network. There is no available exploit.
The affected component should be upgraded.
GHSA
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
ghsa_unreviewed·2026-07-04
CVE-2026-53362 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
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 unprivileg
Red Hat
kernel: kernel: ipv6 frag escape
vendor_redhat·2026-06-21·CVSS 7.8
CVE-2026-53362 [HIGH] CWE-130 kernel: kernel: ipv6 frag escape
kernel: kernel: ipv6 frag escape
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
s
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-53362 kernel: ipv6: account for fraggap on the paged allocation path
bugzilla·2026-07-04
CVE-2026-53362 [HIGH] CVE-2026-53362 kernel: ipv6: account for fraggap on the paged allocation path
CVE-2026-53362 kernel: ipv6: account for fraggap on the paged allocation path
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
Bugzilla
CVE-2026-53362 kernel: kernel: ipv6 frag escape
bugzilla·2026-07-01
CVE-2026-53362 [HIGH] CVE-2026-53362 kernel: kernel: ipv6 frag escape
CVE-2026-53362 kernel: kernel: ipv6 frag escape
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
https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993dhttps://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0ahttps://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769https://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5https://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74e
2026-07-04
Published