octeontx2-pf: avoid double free of pool->stack on AQ init failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: avoid double free of pool->stack on AQ init failure otx2_pool_aq_init() frees pool->stack when mailbox sync or retry allocation fails, but leaves the pointer unchanged. Later, otx2_sq_aura_pool_init() unwinds the partial setup through otx2_aura_pool_free(), which frees pool->stack again. The CN20K-specific cn20k_pool_aq_init() implementation has the same bug in its corresponding error path. Set pool->stack to NULL immediately after the local free so the shared cleanup path does not free the same stack again while cleaning up partially initialized pool state. 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-rc3. Runtime validation was not performed because reproducing this path requires OcteonTX2/CN20K hardware.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in e6e9bc0bf963662b7042048ab0281014625d4cb4; From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in b92e7ea408b6f1144648909c9c49a55d245d7300; From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in 94192b0579333c3deee2441379aab8ca98fc2e6b; From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in 4c29603498b05c049dbbbc47e882f2fbf0193cd7; From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in 0488a0bb344fb1992853b60082acff6be8164d74; From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in 0d9b9d7dbef976ae7f855b6358f1d703014e96ea; From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in c4b8c5d51632538b19ee01cf6d70cbceeefbd3ec; From caa2da34fd25a37e9fd43343b6966fb9d730a6d5 · fixed in 9b244c242bec48b37e82b89787afd6a4c43457e1
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.93; From 6.13.0 · fixed in 6.18.35; From 6.19.0 · fixed in 7.0.11
References 8
git.kernel.org
- stable/c/e6e9bc0bf963662b7042048ab0281014625d4cb4
- stable/c/b92e7ea408b6f1144648909c9c49a55d245d7300
- stable/c/94192b0579333c3deee2441379aab8ca98fc2e6b
- stable/c/4c29603498b05c049dbbbc47e882f2fbf0193cd7
- stable/c/0488a0bb344fb1992853b60082acff6be8164d74
- stable/c/0d9b9d7dbef976ae7f855b6358f1d703014e96ea
- stable/c/c4b8c5d51632538b19ee01cf6d70cbceeefbd3ec
- stable/c/9b244c242bec48b37e82b89787afd6a4c43457e1