CVE-2026-97506crypto: ixp4xx - fix buffer chain unwind on allocation failure
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 95% 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: crypto: ixp4xx - fix buffer chain unwind on allocation failure chainup_buffers() builds a linked list of buffer descriptors for a scatterlist. If dma_pool_alloc() fails while constructing the list, the current code sets buf to NULL and later dereferences it unconditionally at the end of the function: buf->next = NULL; buf->phys_next = 0; This can lead to a null-pointer dereference on allocation failure. If the failure happens after part of the descriptor chain has already been allocated and DMA-mapped, the partially constructed chain also needs to be released. Fix this by terminating the partially constructed chain on allocation failure and letting the callers unwind it via their existing cleanup paths. Also fix ablk_perform() to preserve the hook pointers before checking for failure, so partially built chains can be freed correctly.
Timeline
ID reserved
By Linux
Published
- 9 days later
· 9 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 0d44dc59b2b434b29aafeae581d06f81efac7c83 – < d4007867be42d71795b78fa7f8ce7514dda9ca83
- affected 0d44dc59b2b434b29aafeae581d06f81efac7c83 – < 4918b0bd7d2baafb45d87dca9e322137c96005c2
- affected 0d44dc59b2b434b29aafeae581d06f81efac7c83 – < 8c37bc8d6a6f77bf9593fb1bcab6c14c7cf02991
- affected 0d44dc59b2b434b29aafeae581d06f81efac7c83 – < 04cb00106ca4d0fa9eca24cadc4eda6036e855c8
- affected 0d44dc59b2b434b29aafeae581d06f81efac7c83 – < 028a7f4f3d69e551f6bf9f728d547bbf4cfc707d
- affected 0d44dc59b2b434b29aafeae581d06f81efac7c83 – < 25056329384010a8672552b134f609601dc4f80e
- affected 5a80273150a8a1725fa70418d106eb1f2ee8fd2f
- affected 82a8becb9c2c52fc5e67057a43aeded1f0731e7b
- affected 68845515c8b11791b547a2838e22c27dfa3115ee
- affected 2.6.27.22 – < 2.6.28
- affected 2.6.28.10 – < 2.6.29
- affected 2.6.29.3 – < 2.6.30
- affected 2.6.30
- unaffected < 2.6.30
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/d4007867be42d71795b78fa7f8ce7514dda9ca83 (opens in a new tab)
- https://git.kernel.org/stable/c/4918b0bd7d2baafb45d87dca9e322137c96005c2 (opens in a new tab)
- https://git.kernel.org/stable/c/8c37bc8d6a6f77bf9593fb1bcab6c14c7cf02991 (opens in a new tab)
- https://git.kernel.org/stable/c/04cb00106ca4d0fa9eca24cadc4eda6036e855c8 (opens in a new tab)
- https://git.kernel.org/stable/c/028a7f4f3d69e551f6bf9f728d547bbf4cfc707d (opens in a new tab)
- https://git.kernel.org/stable/c/25056329384010a8672552b134f609601dc4f80e (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-86104 (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-97506)Record last updated .