CVE-2026-31429net: skb: fix cross-cache free of KFENCE-allocated skb head
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% 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: net: skb: fix cross-cache free of KFENCE-allocated skb head SKB_SMALL_HEAD_CACHE_SIZE is intentionally set to a non-power-of-2 value (e.g. 704 on x86_64) to avoid collisions with generic kmalloc bucket sizes. This ensures that skb_kfree_head() can reliably use skb_end_offset to distinguish skb heads allocated from skb_small_head_cache vs. generic kmalloc caches. However, when KFENCE is enabled, kfence_ksize() returns the exact requested allocation size instead of the slab bucket size. If a caller (e.g. bpf_test_init) allocates skb head data via kzalloc() and the requested size happens to equal SKB_SMALL_HEAD_CACHE_SIZE, then slab_build_skb() -> ksize() returns that exact value. After subtracting skb_shared_info overhead, skb_end_offset ends up matching SKB_SMALL_HEAD_HEADROOM, causing skb_kfree_head() to incorrectly free the object to skb_small_head_cache instead of back to the original kmalloc cache, resulting in a slab cross-cache free: kmem_cache_free(skbuff_small_head): Wrong slab cache. Expected skbuff_small_head but got kmalloc-1k Fix this by always calling kfree(head) in skb_kfree_head(). This keeps the free path generic and avoids allocator-specific misclassification for KFENCE objects.
Timeline
ID reserved
By Linux
- 42 days later
· 42 days later
Published
- 21 days later
· 21 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 |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected bf9f1baa279f0758dc2297080360c5a616843927 – < 128b03ccb2582a643983a48a37fda58df80edbde
- affected bf9f1baa279f0758dc2297080360c5a616843927 – < 60313768a8edc7094435975587c00c2d7b834083
- affected bf9f1baa279f0758dc2297080360c5a616843927 – < 2d64618ea846d8d033477311f805ca487d6a6696
- affected bf9f1baa279f0758dc2297080360c5a616843927 – < 474e00b935db250cac320d10c1d3cf4e44b46721
- affected bf9f1baa279f0758dc2297080360c5a616843927 – < 0f42e3f4fe2a58394e37241d02d9ca6ab7b7d516
- affected 6.3
- unaffected < 6.3
- unaffected 6.6.136 – ≤ 6.6.*
- unaffected 6.12.82 – ≤ 6.12.*
- unaffected 6.18.23 – ≤ 6.18.*
- unaffected 6.19.13 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References5
- https://git.kernel.org/stable/c/128b03ccb2582a643983a48a37fda58df80edbde (opens in a new tab)
- https://git.kernel.org/stable/c/60313768a8edc7094435975587c00c2d7b834083 (opens in a new tab)
- https://git.kernel.org/stable/c/2d64618ea846d8d033477311f805ca487d6a6696 (opens in a new tab)
- https://git.kernel.org/stable/c/474e00b935db250cac320d10c1d3cf4e44b46721 (opens in a new tab)
- https://git.kernel.org/stable/c/0f42e3f4fe2a58394e37241d02d9ca6ab7b7d516 (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-23816 (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-31429)Record last updated .