CVE-2026-53228
Last modified
CVE-2026-53228 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ipv6: sit: reload inner IPv6 header after GSO offloads ipip6_tunnel_xmit() caches the inner IPv6 header pointer at function entry and continues using it after iptunnel_handle_offloads(). For GSO skbs, iptunnel_handle_offloads() calls skb_header_unclone(). When the skb header is cloned, skb_header_unclone() can call pskb_expand_head(), which may move the skb head. The pskb_expand_head() contract requires pointers into the skb header to be reloaded after the call. If the later skb_realloc_headroom() branch is not taken, SIT uses the stale iph6 pointer to read the inner hop limit and DS field. EPSS estimates a 0.56% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ipv6: sit: reload inner IPv6 header after GSO offloads ipip6_tunnel_xmit() caches the inner IPv6 header pointer at function entry and continues using it after iptunnel_handle_offloads(). For GSO skbs, iptunnel_handle_offloads() calls skb_header_unclone(). When the skb header is cloned, skb_header_unclone() can call pskb_expand_head(), which may move the skb head. The pskb_expand_head() contract requires pointers into the skb header to be reloaded after the call. If the later skb_realloc_headroom() branch is not taken, SIT uses the stale iph6 pointer to read the inner hop limit and DS field. That can read from a freed skb head after the old head's remaining clone is released. Reload iph6 after the offload helper succeeds and before subsequent reads from the inner IPv6 header. Keep the existing reload after skb_realloc_headroom(), since that branch can also replace the skb.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.18, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53228?
How severe is CVE-2026-53228?
How do I fix CVE-2026-53228?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53222In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53223In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53224In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53225In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53226In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53227In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53229In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-5323A vulnerability was found in priyankark a11y-mcp up to 1.0.5…5.3
- CVE-2026-53230In the Linux kernel, the following vulnerability has been re…8.7
- CVE-2026-53231In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53232In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53233In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-53228?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
