LiveActive security incident?Get immediate response
CVE Record

CVE-2024-37021: fpga: manager: add owner module and take its refcount

In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga manager. Other changes: opportunistically move put_device() from __fpga_mgr_get() to fpga_mgr_get() and of_fpga_mgr_get() to improve code clarity since the manager device is taken in these functions.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the FPGA manager subsystem. Under specific driver registration conditions, the kernel can dereference a null pointer while getting an FPGA manager, potentially causing a crash. The sources do not provide CVSS, CWE, or confirmed exploitation evidence.

Executive priority

Treat this as targeted operational risk, not an internet-wide emergency. Patch during normal kernel maintenance, with higher priority for systems controlling FPGA hardware or relying on high availability.

Technical view

The FPGA manager code assumed the parent device driver owner pointer could be used for module refcounting. If the parent device had no driver, manager lookup could hit a null pointer dereference. The fix adds an owner module pointer to fpga_manager and updates registration helpers and documentation.

Likely exposure

Exposure is most likely on Linux systems using FPGA manager functionality, especially embedded, hardware-control, or FPGA-enabled platforms. The source bundle lists Linux as affected across several kernel version contexts, but downstream distribution impact depends on vendor backports.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. The described impact is a kernel null pointer dereference path, which is more consistent with local or device-specific denial-of-service risk than broad remote compromise.

Researcher notes

Evidence is limited to kernel stable commits, CVE metadata, and a Debian LTS advisory reference. No CVSS vector, CWE, exploit status, or detailed attack preconditions are provided in the bundle, so conclusions should remain conservative.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check your Linux distribution advisory for backported fixed packages.
  • Prioritize FPGA-enabled and embedded Linux systems for review.
  • Review out-of-tree FPGA manager drivers for updated registration interfaces.

Validation and detection

  • Inventory systems running Linux kernels in the source-listed affected contexts.
  • Confirm whether FPGA manager support is enabled or used.
  • Verify installed kernels include the referenced stable patch lineage.
  • Check vendor package changelogs for CVE-2024-37021 coverage.
Prepared
Confidence
medium
Sources
7

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-2024-37021 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
6Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux654ba4cc0f3ed7c0f08bfb39f66059d8c42943ee, 654ba4cc0f3ed7c0f08bfb39f66059d8c42943ee, 654ba4cc0f3ed7c0f08bfb39f66059d8c42943ee, 654ba4cc0f3ed7c0f08bfb39f66059d8c42943eeunaffected
LinuxLinux4.4, 0, 6.1.120, 6.6.33, 6.9.4, 6.10affected
Weakness

CWE details

No CWE listed

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