Out-of-bounds write in Linux kernel iavf_get_ethtool_stats()
CVE-2026-31505 is an out-of-bounds write vulnerability in the Linux kernel iavf network driver, specifically in iavf_get_ethtool_stats(). The bug is caused by inconsistent use of queue-count fields across related ethtool handlers: iavf_get_sset_count() and iavf_get_stat_strings() size the statistics buffer using a queue count derived from real_num_tx_queues, while iavf_get_ethtool_stats() iterates using a different runtime-varying queue count such as num_active_queues. During concurrent channel reconfiguration and statistics retrieval, for example simultaneous execution of "ethtool -L" and "ethtool -S", these values can diverge. A documented race occurs when queue/channel counts are changed from 1 to 8: the stats buffer may be allocated for 1 queue while iavf_get_ethtool_stats() writes statistics for 8 queues, resulting in vmalloc out-of-bounds writes. The upstream fix standardizes all related functions on immutable num_tx_queues to eliminate the mismatch.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.