octeontx2-af: fix cn20k mailbox lifetime on repeated rvu_mbox_init()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3b11a77f69980932c3924054d66e565c9a135747, Kernel a0fcbea79f034f49bdd44915f28938922023458d and Kernel c08314f91782983d67af0807ed1360e404ac4a8b.
In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: fix cn20k mailbox lifetime on repeated rvu_mbox_init() rvu_mbox_init() is called separately for AF-PF mailboxes during probe and for AF-VF mailboxes when SR-IOV is enabled. Each call used to allocate a new ng_rvu object, leaking the first allocation when the pointer was overwritten on the second call. Sharing one ng_rvu across both paths exposed several teardown bugs: the error path freed all cn20k mailbox DMA and kfree()d ng_rvu even when only the failing init type should be unwound, leaving live AF-PF mailbox memory in use after an AF-VF init failure. mutex_init() was also re-run on the AF-VF path while AF-PF mailbox handlers could still hold rvu->mbox_lock. Probe and SR-IOV failure paths did not release cn20k mailbox DMA either, since cleanup only happened in rvu_remove(). Allocate ng_rvu once with devm_kzalloc(), initialize mbox_lock in the same block, unwind only the mailbox memory for the failing init type, and free cn20k mailbox DMA from the probe and pci_enable_sriov() error paths.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=e53ee4acb220acab6832669334279367b0206af6 <3b11a77f69980932c3924054d66e565c9a135747, >=e53ee4acb220acab6832669334279367b0206af6 <a0fcbea79f034f49bdd44915f28938922023458d, >=e53ee4acb220acab6832669334279367b0206af6 <c08314f91782983d67af0807ed1360e404ac4a8b | 3b11a77f69980932c3924054d66e565c9a135747, a0fcbea79f034f49bdd44915f28938922023458d, c08314f91782983d67af0807ed1360e404ac4a8b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket