CVE-2026-46300
Last modified
CVE-2026-46300 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skb_try_coalesce() can attach paged frags from @from to @to. If @from has SKBFL_SHARED_FRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost. That breaks the invariant relied on by later in-place writers. EPSS estimates a 3.66% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skb_try_coalesce() can attach paged frags from @from to @to. If @from has SKBFL_SHARED_FRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost. That breaks the invariant relied on by later in-place writers. In particular, ESP input checks skb_has_shared_frag() before deciding whether an uncloned nonlinear skb can skip skb_cow_data(). If TCP receive coalescing has moved shared frags into an unmarked skb, ESP can see skb_has_shared_frag() as false and decrypt in place over page-cache backed frags. Propagate SKBFL_SHARED_FRAG when skb_try_coalesce() transfers paged frags. The tailroom copy path does not need the marker because it copies bytes into @to's linear data rather than transferring frag descriptors.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.9, <= 5.10.257 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.208 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.174 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.141 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.91 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.33 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-46300?
How severe is CVE-2026-46300?
How do I fix CVE-2026-46300?
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-46295In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46296In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46297In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46298In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-46299In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-4630A flaw was found in Keycloak. An authenticated client could …6.8
- CVE-2026-46301In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46302In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46303In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-46304In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-46305In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46306In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2026-46300?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
