CVE-2026-72023octeontx2-pf: fix SQB pointer leak on init failure
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% 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: octeontx2-pf: fix SQB pointer leak on init failure otx2_init_hw_resources() initializes SQ aura and pool resources before several later setup steps. On failure, err_free_sq_ptrs only frees SQB pages, leaving the per-SQ sqb_ptrs arrays behind. Use otx2_free_sq_res() for the SQ unwind path and let it free sqb_ptrs even when sq->sqe has not been allocated yet. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1.1. An x86_64 allyesconfig build showed no new warnings. As we do not have an OcteonTX2 PF device and the corresponding AF mailbox setup to test with, no runtime testing was able to be performed.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 8 days later
· 8 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.22% · top 88% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < fca9c22633169a6c5d429a32e439121b6419e2be
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < 42c2836f10ac0427dac9e9a923d6ee2189dec544
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < 2cac2eac935ed7e0a9203204e036a1f6090ebc3d
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < 148d7ec0a3a98839c320e6cdd112e2e88bfb091b
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < 5e023fe2569e630ba23b5558ebe4bf4837af4d16
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < 5df30f05db96552903680a17f858d250dfd9e86e
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < 23d917acd9c9a9fd999688ec3fdde7aa58ab8a14
- affected caa2da34fd25a37e9fd43343b6966fb9d730a6d5 – < 62e7df6d042aeebd5efb581074e28865c04477be
- affected 5.6
- unaffected < 5.6
- unaffected 5.10.266 – ≤ 5.10.*
- unaffected 5.15.217 – ≤ 5.15.*
- unaffected 6.1.184 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/fca9c22633169a6c5d429a32e439121b6419e2be (opens in a new tab)
- https://git.kernel.org/stable/c/42c2836f10ac0427dac9e9a923d6ee2189dec544 (opens in a new tab)
- https://git.kernel.org/stable/c/2cac2eac935ed7e0a9203204e036a1f6090ebc3d (opens in a new tab)
- https://git.kernel.org/stable/c/148d7ec0a3a98839c320e6cdd112e2e88bfb091b (opens in a new tab)
- https://git.kernel.org/stable/c/5e023fe2569e630ba23b5558ebe4bf4837af4d16 (opens in a new tab)
- https://git.kernel.org/stable/c/5df30f05db96552903680a17f858d250dfd9e86e (opens in a new tab)
- https://git.kernel.org/stable/c/23d917acd9c9a9fd999688ec3fdde7aa58ab8a14 (opens in a new tab)
- https://git.kernel.org/stable/c/62e7df6d042aeebd5efb581074e28865c04477be (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-58981 (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-72023)Record last updated .