Bug 2506796 (CVE-2026-64224) - CVE-2026-64224 kernel: octeontx2-pf: fix double free in rvu_rep_rsrc_init()
Summary: CVE-2026-64224 kernel: octeontx2-pf: fix double free in rvu_rep_rsrc_init()
Keywords:
Status: NEW
Alias: CVE-2026-64224
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-24 16:03 UTC by OSIDB Bzimport
Modified: 2026-07-28 10:04 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-24 16:03:31 UTC
In the Linux kernel, the following vulnerability has been resolved:

octeontx2-pf: fix double free in rvu_rep_rsrc_init()

rvu_rep_rsrc_init() allocates queue memory before calling
otx2_init_hw_resources(). When hardware resource setup fails,
otx2_init_hw_resources() already unwinds the partially initialized
SQ, CQ, and aura state before returning an error. The representor
error path then calls otx2_free_hw_resources() again and can free
the same resources a second time.

Fix this by splitting the cleanup labels so that a failure from
otx2_init_hw_resources() only releases queue memory. Keep the
otx2_free_hw_resources() call for failures that happen after
hardware resource initialization completed successfully.

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 representor hardware.

Comment 1 Mauro Matteo Cascella 2026-07-28 10:03:14 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026072417-CVE-2026-64224-f7a2@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.