LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47283: net:sfc: fix non-freed irq in legacy irq mode

In the Linux kernel, the following vulnerability has been resolved: net:sfc: fix non-freed irq in legacy irq mode SFC driver can be configured via modparam to work using MSI-X, MSI or legacy IRQ interrupts. In the last one, the interrupt was not properly released on module remove. It was not freed because the flag irqs_hooked was not set during initialization in the case of using legacy IRQ. Example of (trimmed) trace during module remove without this fix: remove_proc_entry: removing non-empty directory 'irq/125', leaking at least '0000:3b:00.1' WARNING: CPU: 39 PID: 3658 at fs/proc/generic.c:715 remove_proc_entry+0x15c/0x170 ...trimmed... Call Trace: unregister_irq_proc+0xe3/0x100 free_desc+0x29/0x70 irq_free_descs+0x47/0x70 mp_unmap_irq+0x58/0x60 acpi_unregister_gsi_ioapic+0x2a/0x40 acpi_pci_irq_disable+0x78/0xb0 pci_disable_device+0xd1/0x100 efx_pci_remove+0xa1/0x1e0 [sfc] pci_device_remove+0x38/0xa0 __device_release_driver+0x177/0x230 driver_detach+0xcb/0x110 bus_remove_driver+0x58/0xd0 pci_unregister_driver+0x2a/0xb0 efx_exit_module+0x24/0xf40 [sfc] __do_sys_delete_module.constprop.0+0x171/0x280 ? exit_to_user_mode_prepare+0x83/0x1d0 do_syscall_64+0x3d/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f9f9385800b ...trimmed...

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver cleanup bug in the Solarflare SFC network driver. When configured for legacy IRQ interrupts, removing the module could leave an interrupt resource unreleased. The source does not show remote compromise, data exposure, or active exploitation.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency, based on available sources. Prioritize systems with Solarflare SFC adapters and legacy IRQ configuration, especially production hosts where module unload or device removal occurs.

Technical view

The SFC driver failed to set irqs_hooked during legacy IRQ initialization, so module removal skipped proper IRQ release. The reported trace shows procfs IRQ cleanup warnings during efx_pci_remove and module deletion. Fixes are linked in stable kernel commits.

Likely exposure

Exposure appears limited to systems using the Linux SFC network driver with legacy IRQ mode, especially where the module is removed or devices are detached. Most environments not using this driver or interrupt mode are unlikely to be exposed.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The described behavior is a local driver resource cleanup failure during module removal, not a demonstrated remote attack path.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. No CVSS, CWE, exploitability assessment, or vendor-specific package matrix is included. Validate affected status against downstream kernel backports rather than upstream version numbers alone.

Mitigation direction

  • Apply the relevant Linux stable kernel update containing the referenced SFC driver fix.
  • Check distribution kernel advisories for the exact fixed package version.
  • Avoid legacy IRQ mode for SFC devices where operationally feasible.
  • Plan remediation through normal kernel maintenance unless vendor guidance raises severity.

Validation and detection

  • Identify hosts using the sfc kernel module and Solarflare network adapters.
  • Check whether SFC is configured for legacy IRQ rather than MSI or MSI-X.
  • Confirm kernel version or vendor package includes the referenced stable fix.
  • Review logs for IRQ proc cleanup warnings during sfc module removal.
Prepared
Confidence
medium
Sources
5

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-47283 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe6a43910d55d09dae65772ad571d4c61e459b17a, e6a43910d55d09dae65772ad571d4c61e459b17a, e6a43910d55d09dae65772ad571d4c61e459b17aunaffected
LinuxLinux5.9, 0, 5.10.44, 5.12.11, 5.13affected
Weakness

CWE details

No CWE listed

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