octeontx2-pf: fix SQB pointer leak on init failure
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.
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.6affected
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before fca9c22633169a6c5d429a32e439121b6419e2beaffected · git
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before 42c2836f10ac0427dac9e9a923d6ee2189dec544affected · git
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before 2cac2eac935ed7e0a9203204e036a1f6090ebc3daffected · git
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before 148d7ec0a3a98839c320e6cdd112e2e88bfb091baffected · git
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before 5e023fe2569e630ba23b5558ebe4bf4837af4d16affected · git
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before 5df30f05db96552903680a17f858d250dfd9e86eaffected · git
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before 23d917acd9c9a9fd999688ec3fdde7aa58ab8a14affected · git
- caa2da34fd25a37e9fd43343b6966fb9d730a6d5 and later · before 62e7df6d042aeebd5efb581074e28865c04477beaffected · git
- before 5.6not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 148d7ec0a3a98839c320e6cdd112e2e88bfb091b | Vendor (CNA) |
| Linux Linux | 23d917acd9c9a9fd999688ec3fdde7aa58ab8a14 | Vendor (CNA) |
| Linux Linux | 2cac2eac935ed7e0a9203204e036a1f6090ebc3d | Vendor (CNA) |
| Linux Linux | 42c2836f10ac0427dac9e9a923d6ee2189dec544 | Vendor (CNA) |
| Linux Linux | 5df30f05db96552903680a17f858d250dfd9e86e | Vendor (CNA) |
| Linux Linux | 5e023fe2569e630ba23b5558ebe4bf4837af4d16 | Vendor (CNA) |
| Linux Linux | 62e7df6d042aeebd5efb581074e28865c04477be | Vendor (CNA) |
| Linux Linux | fca9c22633169a6c5d429a32e439121b6419e2be | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/148d7ec0a3a98839c320e6cdd112e2e88bfb091b
- git.kernel.org/stable/c/23d917acd9c9a9fd999688ec3fdde7aa58ab8a14
- git.kernel.org/stable/c/2cac2eac935ed7e0a9203204e036a1f6090ebc3d
- git.kernel.org/stable/c/42c2836f10ac0427dac9e9a923d6ee2189dec544
- git.kernel.org/stable/c/5df30f05db96552903680a17f858d250dfd9e86e
- git.kernel.org/stable/c/5e023fe2569e630ba23b5558ebe4bf4837af4d16
- git.kernel.org/stable/c/62e7df6d042aeebd5efb581074e28865c04477be
- git.kernel.org/stable/c/fca9c22633169a6c5d429a32e439121b6419e2be
Vendor advisories and official records. Exploit/PoC links are deliberately left out.