CVE-2022-49027: iavf: Fix error handling in iavf_init_module()
In the Linux kernel, the following vulnerability has been resolved:
iavf: Fix error handling in iavf_init_module()
The iavf_init_module() won't destroy workqueue when pci_register_driver()
failed. Call destroy_workqueue() when pci_register_driver() failed to
prevent the resource leak.
Similar to the handling of u132_hcd_init in commit f276e002793c
("usb: u132-hcd: fix resource leak")
Security readout for executives and security teams
Plain-English summary
CVE-2022-49027 is a Linux kernel resource-leak bug in the iavf network driver initialization path. If PCI driver registration fails, a workqueue may not be destroyed. The sources do not provide CVSS, confirmed exploitation, or broad operational impact, so urgency depends on affected kernel use and vendor backport status.
Executive priority
Treat this as routine kernel hygiene unless affected iavf-dependent infrastructure is identified. There is no sourced evidence of active exploitation, but unpatched kernel resource leaks should still be closed through standard maintenance windows.
Technical view
The issue is in iavf_init_module(). The kernel fix adds destroy_workqueue() when pci_register_driver() fails, preventing leaked kernel resources during module initialization failure. Public records identify affected Linux kernel versions and stable commits, but do not describe privilege requirements, triggerability, or security impact beyond resource leakage.
Likely exposure
Exposure is most plausible on Linux systems running affected kernel builds with the iavf driver available or used for Intel adaptive virtual function networking. Systems on vendor kernels may already carry backported fixes, so package changelogs matter more than upstream version strings alone.
Exploitation context
The provided sources do not show active exploitation, proof-of-concept activity, or CISA KEV listing. The described condition is an error-handling resource leak during driver initialization failure, not a documented remote compromise path.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. Key unknowns include practical trigger conditions, local versus privileged access assumptions, and measurable denial-of-service impact. Avoid overstating risk without vendor advisories or additional kernel analysis.
Mitigation direction
Update to a vendor-supported kernel containing the stable iavf fix.
Check Linux distribution advisories and package changelogs for CVE-2022-49027 backports.
Prioritize hosts using iavf, SR-IOV virtual functions, or Intel virtual networking.
Keep normal kernel reboot and maintenance procedures aligned with vendor guidance.
Validation and detection
Inventory kernel versions and vendor package release levels across Linux hosts.
Check whether the iavf module is present, loaded, or required on each host.
Confirm vendor kernel notes reference CVE-2022-49027 or the linked stable commits.
Verify vulnerability scanner findings against distro backport metadata before escalating.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49027 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.