CVE-2026-23254
Last modified
CVE-2026-23254 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: gro: fix outer network offset The udp GRO complete stage assumes that all the packets inserted the RX have the `encapsulation` flag zeroed. Such assumption is not true, as a few H/W NICs can set such flag when H/W offloading the checksum for an UDP encapsulated traffic, the tun driver can inject GSO packets with UDP encapsulation and the problematic layout can also be created via a veth based setup. Due to the above, in the problematic scenarios, udp4_gro_complete() uses the wrong network offset (inner instead of outer) to compute the outer UDP header pseudo checksum, leading to csum validation errors later on in packet processing. Address the issue always clearing the encapsulation flag at GRO completion time. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: gro: fix outer network offset The udp GRO complete stage assumes that all the packets inserted the RX have the `encapsulation` flag zeroed. Such assumption is not true, as a few H/W NICs can set such flag when H/W offloading the checksum for an UDP encapsulated traffic, the tun driver can inject GSO packets with UDP encapsulation and the problematic layout can also be created via a veth based setup. Due to the above, in the problematic scenarios, udp4_gro_complete() uses the wrong network offset (inner instead of outer) to compute the outer UDP header pseudo checksum, leading to csum validation errors later on in packet processing. Address the issue always clearing the encapsulation flag at GRO completion time. Such flag will be set again as needed for encapsulated packets by udp_gro_complete().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.31, < 6.6.124 | — |
| Linux | Linux Kernel | >= 6.8.10, < 6.9 | — |
| Linux | Linux Kernel | >= 6.9.1, < 6.12.70 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.10 | — |
| Linux | Linux Kernel | 6.9 | — |
| Linux | Linux Kernel | 6.19 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-23254?
How severe is CVE-2026-23254?
How do I fix CVE-2026-23254?
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-23249In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2325Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13, 1…6.5
- CVE-2026-23250In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23251In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23252In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23253In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23255In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23256In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23257In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23258In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23259In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2326Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
Are you affected by CVE-2026-23254?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
