CVE-2022-50066 is an out-of-bounds array access in the Linux kernel Aquantia Atlantic Ethernet driver. In the driver stop/suspend handling path, the final update expression of a for loop can increment the vector index beyond the bounds of the aq_vec pointer array. The code subsequently dereferences self->aq_vec[i] without confirming that the index remains valid. UBSAN observed access to index 8 of an eight-element aq_vec array. The correction changes the unsafe loop logic and analogous loop patterns in the driver.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-range index error in the Linux kernel Atlantic network driver aq_vec handling.
An index-out-of-range error in the Linux kernel Atlantic network driver aq_vec handling.
An index-out-of-range vulnerability in the Linux kernel Atlantic network driver involving aq_vec indexing.
An out-of-range index vulnerability in the Linux kernel Atlantic network driver involving aq_vec indexing.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.