Network-service interruption via repeated VF master aborts
Published Feb 9, 2022 · Updated May 5, 2025
Insufficient control flow management in Intel 82599 controllers with ixgbe drivers before 5.13.4 allows local users to interrupt network service. The ixgbe physical-function driver fails to disable a virtual function that repeatedly triggers PCI master-abort MDD events, allowing continued fault handling. Exploitation requires local authenticated control of an SR-IOV virtual function on affected hardware; published evidence does not identify a system crash.
Summary
What happened
Insufficient control flow management in Intel 82599 controllers with ixgbe drivers before 5.13.4 allows local users to interrupt network service. The ixgbe physical-function driver fails to disable a virtual function that repeatedly triggers PCI master-abort MDD events, allowing continued fault handling. Exploitation requires local authenticated control of an SR-IOV virtual function on affected hardware; published evidence does not identify a system crash.
The record
- CVE
- CVE-2021-33061
- Published
- Feb 9, 2022
- Updated
- May 5, 2025
- Vendor
- Intel Corporation
- Product
- Intel 82599 10 Gigabit Ethernet Controller
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 9, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See references
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo