CVE-2026-93105
Last modified
CVE-2026-93105 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: esp: do not unref managed frag pages in esp_ssg_unref() esp_ssg_unref() releases the page references held on the source scatterlist after the AEAD operation completes. It calls skb_page_unref() on every frag page for an out-of-place transform (req->src != req->dst), and in the error path of esp_output_tail() (already_unref == true) on the request's own scatterlist. This is wrong when the skb carries managed frags (SKBFL_MANAGED_FRAG_REFS).
Description
In the Linux kernel, the following vulnerability has been resolved: esp: do not unref managed frag pages in esp_ssg_unref() esp_ssg_unref() releases the page references held on the source scatterlist after the AEAD operation completes. It calls skb_page_unref() on every frag page for an out-of-place transform (req->src != req->dst), and in the error path of esp_output_tail() (already_unref == true) on the request's own scatterlist. This is wrong when the skb carries managed frags (SKBFL_MANAGED_FRAG_REFS). Managed frags are owned by a zerocopy ubuf and the skb does not hold a per-frag page reference; io_uring SEND_ZC with a registered buffer attaches the bvec pages this way via io_sg_from_iter(). The rest of the stack honours this invariant: skb_release_data() skips the per-frag unref when SKBFL_MANAGED_FRAG_REFS is set, and skb_zcopy_managed() is the guard used at the other unref sites. esp_ssg_unref() is missing that guard, so for a managed-frag skb it drops a page reference the skb never acquired. This can underflow the page reference count and free a page that is still in use. Guard the function with skb_zcopy_managed() so both unref paths are skipped for managed-frag skbs, matching skb_release_data().
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < 26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf; >= cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < 21697720ff43b8dfa25b8e8d9ca7f56f4597fc80 |
| Linux | Linux | 4.11 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93105?
How severe is CVE-2026-93105?
How do I fix CVE-2026-93105?
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-93099In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93100In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93101In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93102In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93103In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93104In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93106In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93107In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-93108In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93109In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9311IBM WebSphere Application Server 9.0, and 8.5 is vulnerable …9
- CVE-2026-93110In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-93105?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
