LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46914: ixgbe: fix unbalanced device enable/disable in suspend/resume

In the Linux kernel, the following vulnerability has been resolved: ixgbe: fix unbalanced device enable/disable in suspend/resume pci_disable_device() called in __ixgbe_shutdown() decreases dev->enable_cnt by 1. pci_enable_device_mem() which increases dev->enable_cnt by 1, was removed from ixgbe_resume() in commit 6f82b2558735 ("ixgbe: use generic power management"). This caused unbalanced increase/decrease. So add pci_enable_device_mem() back. Fix the following call trace. ixgbe 0000:17:00.1: disabling already-disabled device Call Trace: __ixgbe_shutdown+0x10a/0x1e0 [ixgbe] ixgbe_suspend+0x32/0x70 [ixgbe] pci_pm_suspend+0x87/0x160 ? pci_pm_freeze+0xd0/0xd0 dpm_run_callback+0x42/0x170 __device_suspend+0x114/0x460 async_suspend+0x1f/0xa0 async_run_entry_fn+0x3c/0xf0 process_one_work+0x1dd/0x410 worker_thread+0x34/0x3f0 ? cancel_delayed_work+0x90/0x90 kthread+0x14c/0x170 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x30

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel ixgbe driver suspend/resume defect. The cited issue is an unbalanced PCI device enable/disable sequence that can produce kernel call traces during power-management transitions. The public bundle does not establish remote attackability, data exposure, or active exploitation.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize patch verification for servers using ixgbe hardware or power-management transitions, especially where kernel reliability matters.

Technical view

Commit 6f82b2558735 removed pci_enable_device_mem() from ixgbe_resume(), while __ixgbe_shutdown() still called pci_disable_device(). This left device enable counts unbalanced across suspend/resume. Stable fixes restore pci_enable_device_mem() to balance the lifecycle and address the reported already-disabled-device trace.

Likely exposure

Exposure is most likely limited to Linux systems using the ixgbe driver and affected kernel builds listed in the bundle, including 5.9, 5.10.32, 5.11.16, and 5.12. Distribution backports may change practical exposure.

Exploitation context

The bundle reports no KEV listing, no CVSS score, and no cited active exploitation. Evidence describes a kernel driver power-management fault, not a confirmed exploitable intrusion path.

Researcher notes

The source evidence is limited to the kernel fix description and stable commit references. No CWE, CVSS vector, exploit status, or detailed impact statement is provided, so severity and attack prerequisites remain uncertain.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Check your Linux distribution advisory for exact fixed package versions.
  • Prioritize systems using the ixgbe driver and suspend/resume workflows.
  • If no patch status is clear, seek vendor guidance before applying workarounds.

Validation and detection

  • Inventory Linux hosts using the ixgbe driver.
  • Compare installed kernels against vendor CVE status and fixed builds.
  • Review logs for the reported already-disabled-device ixgbe trace.
  • Confirm the updated kernel includes the referenced stable fix commits.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2021-46914 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6f82b25587354ce7c9c42e0b53d8b0770b900847, 6f82b25587354ce7c9c42e0b53d8b0770b900847, 6f82b25587354ce7c9c42e0b53d8b0770b900847unaffected
LinuxLinux5.9, 0, 5.10.32, 5.11.16, 5.12affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.