CVE-2026-72023

octeontx2-pf: fix SQB pointer leak on init failure

N/A
Published: August 15, 2026 at 05:51 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.6 ≤ v < 5.10.2665.6 ≤ v < 5.15.2175.6 ≤ v < 6.1.1845.6 ≤ v < 6.12.1015.6 ≤ v < 6.18.405.6 ≤ v < 6.6.1485.6 ≤ v < 7.1.55.6 ≤ v < 7.25.6caa2da34fd25a37e9fd43343b6966fb9d730a6d5
Vendor states this is fixed in 148d7ec0a3a98839c320e6cdd112e2e88bfb091b (fixed)
Vendor states this is fixed in 23d917acd9c9a9fd999688ec3fdde7aa58ab8a14 (fixed)
Vendor states this is fixed in 2cac2eac935ed7e0a9203204e036a1f6090ebc3d (fixed)
Vendor states this is fixed in 42c2836f10ac0427dac9e9a923d6ee2189dec544 (fixed)
Vendor states this is fixed in 5df30f05db96552903680a17f858d250dfd9e86e (fixed)
Vendor states this is fixed in 5e023fe2569e630ba23b5558ebe4bf4837af4d16 (fixed)
Vendor states this is fixed in 62e7df6d042aeebd5efb581074e28865c04477be (fixed)
Vendor states this is fixed in fca9c22633169a6c5d429a32e439121b6419e2be (fixed)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card