CVE-2026-90079
Last modified
CVE-2026-90079 is a vulnerability of currently unknown severity. 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.
Description
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= e53ee4acb220acab6832669334279367b0206af6, < a0fcbea79f034f49bdd44915f28938922023458d; >= e53ee4acb220acab6832669334279367b0206af6, < 3b11a77f69980932c3924054d66e565c9a135747 |
| Linux | Linux | 6.17 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90079?
How severe is CVE-2026-90079?
How do I fix CVE-2026-90079?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90073In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90074In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90075In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90076In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90077In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90078In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9008The Page-list plugin for WordPress is vulnerable to Missing …4.3
- CVE-2026-90080In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90081In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90082In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90083In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90084In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-90079?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
