CVE-2026-53362
ipv6: account for fraggap on the paged allocation path
Description
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.
INFO
Published Date :
July 4, 2026, 12:17 p.m.
Last Modified :
July 22, 2026, 7:07 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Update the Linux kernel to include the fix.
- Ensure accounting correctly handles fraggap.
- Verify skb linear area size calculation.
- Remove stale comments and checks.
Public PoC/Exploit Available at Github
CVE-2026-53362 has a 2 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53362.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53362 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53362
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Look for possible escape vectors from a container
aws azure cicd devsecops docker kubernetes kubernetes-security cve-scanning kernel-hardening kernel-security container-security linux linux-kernel
Shell
DSA and DLA for Debian last 14 days
Python
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53362 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53362 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 22, 2026
Action Type Old Value New Value Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.144 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.95 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.38 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.1.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.0 up to (excluding) 6.1.177 Added Reference Type kernel.org: https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74e Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 18, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 04, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '773ba4fe9104a64a54d1c00f0fb6ffb95def2b03', 'lessThan': '14200d435af9a9eeb444f529fc2f689a236b7962', 'versionType': 'git'}, {'status': 'affected', 'version': '773ba4fe9104a64a54d1c00f0fb6ffb95def2b03', 'lessThan': '65fb14cbebb0cd0eff903a22d33537ddc8b95769', 'versionType': 'git'}, {'status': 'affected', 'version': '773ba4fe9104a64a54d1c00f0fb6ffb95def2b03', 'lessThan': '46f201f8b4c39633a1fa3dc12459f506d470993d', 'versionType': 'git'}, {'status': 'affected', 'version': '773ba4fe9104a64a54d1c00f0fb6ffb95def2b03', 'lessThan': '6374fb9edf72c67a118a2c214a0dddd04c921e0a', 'versionType': 'git'}, {'status': 'affected', 'version': '773ba4fe9104a64a54d1c00f0fb6ffb95def2b03', 'lessThan': 'e9eacf19281ea2498b36291b56c9606118c2d74e', 'versionType': 'git'}, {'status': 'affected', 'version': '773ba4fe9104a64a54d1c00f0fb6ffb95def2b03', 'lessThan': '736b380e28d0480c7bc3e022f1950f31fe53a7c5', 'versionType': 'git'}], 'programFiles': ['net/ipv6/ip6_output.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.0'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.0', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.1.177', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.144', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.95', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.38', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.3', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/ipv6/ip6_output.c'], 'defaultStatus': 'affected'}] Added Description 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. Added Reference https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962 Added Reference https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d Added Reference https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a Added Reference https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769 Added Reference https://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5 Added Reference https://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74e