CVE-2026-93105esp: do not unref managed frag pages in esp_ssg_unref()
- 7.8HighCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected cac2661c53f35cbe651bef9b07026a5a05ab8ce0 – < cb375965800d474c0281a2e92c43c724fce9f463
- affected cac2661c53f35cbe651bef9b07026a5a05ab8ce0 – < 201bdf10ae92e7cbd524adf8c0323e2a963d5fd7
- affected cac2661c53f35cbe651bef9b07026a5a05ab8ce0 – < 3ec55f0c8a6a543cf660584d1346e11f6311ee59
- affected cac2661c53f35cbe651bef9b07026a5a05ab8ce0 – < 1ad6456898f6e6cf58be83bdb607acb1119a9cd1
- affected cac2661c53f35cbe651bef9b07026a5a05ab8ce0 – < 26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf
- affected cac2661c53f35cbe651bef9b07026a5a05ab8ce0 – < 21697720ff43b8dfa25b8e8d9ca7f56f4597fc80
- affected 4.11
- unaffected < 4.11
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/cb375965800d474c0281a2e92c43c724fce9f463 (opens in a new tab)
- https://git.kernel.org/stable/c/201bdf10ae92e7cbd524adf8c0323e2a963d5fd7 (opens in a new tab)
- https://git.kernel.org/stable/c/3ec55f0c8a6a543cf660584d1346e11f6311ee59 (opens in a new tab)
- https://git.kernel.org/stable/c/1ad6456898f6e6cf58be83bdb607acb1119a9cd1 (opens in a new tab)
- https://git.kernel.org/stable/c/26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf (opens in a new tab)
- https://git.kernel.org/stable/c/21697720ff43b8dfa25b8e8d9ca7f56f4597fc80 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82213 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93105)Record last updated .