LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible

In the Linux kernel, the following vulnerability has been resolved: scsi: qedf: Make qedf_execute_tmf() non-preemptible Stop calling smp_processor_id() from preemptible code in qedf_execute_tmf90. This results in BUG_ON() when running an RT kernel. [ 659.343280] BUG: using smp_processor_id() in preemptible [00000000] code: sg_reset/3646 [ 659.343282] caller is qedf_execute_tmf+0x8b/0x360 [qedf]

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects a specific storage driver path. On real-time kernels, the qedf driver can trigger a kernel BUG because it calls a CPU-local function from preemptible code. The likely business impact is service instability or crash on exposed systems, not confirmed remote compromise.

Executive priority

Treat as targeted operational risk for Linux storage infrastructure, especially RT kernels. It does not currently justify emergency response without matching exposure, but affected systems should enter normal kernel patch cycles with priority for availability-sensitive hosts.

Technical view

CVE-2024-42124 fixes qedf_execute_tmf() in the Linux SCSI qedf driver by making the task management function path non-preemptible. The reported failure is a BUG_ON from smp_processor_id() used in preemptible code, observed during sg_reset on an RT kernel.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the qedf SCSI/Fibre Channel driver present and relevant operations on an RT kernel. General Linux hosts without this driver or hardware path are less likely to be exposed. Exact distro package exposure requires vendor advisory verification.

Exploitation context

The bundle does not show KEV listing, public exploitation, CVSS, CWE, or a weaponized exploit. Evidence supports a stability bug reachable in a specific kernel driver context, with the example failure occurring during sg_reset on an RT kernel.

Researcher notes

The CVE data is sparse: no CVSS, CWE, exploit status, or detailed affected range semantics are provided. Analysis should focus on commit presence, distro backports, qedf module usage, RT kernel configuration, and kernel log evidence rather than assuming broad Linux exposure.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable qedf fixes.
  • Check Debian LTS and other distro advisories for backported package names.
  • If qedf is unnecessary, follow vendor guidance on disabling unused storage drivers.
  • Prioritize affected RT kernel systems tied to storage availability.
  • Do not deploy by direct kernel patching without distro or vendor validation.

Validation and detection

  • Inventory kernel versions against the affected streams in the CVE record.
  • Check whether the qedf module is present, loaded, or required.
  • Review kernel logs for the cited smp_processor_id preemptible BUG pattern.
  • Confirm the relevant stable commit or distro backport is included.
  • Validate storage workflows after kernel update in staging.
Prepared
Confidence
medium
Sources
10

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-2024-42124 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
9Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux61d8658b4a435eac729966cc94cdda077a8df5cd, 61d8658b4a435eac729966cc94cdda077a8df5cd, 61d8658b4a435eac729966cc94cdda077a8df5cd, 61d8658b4a435eac729966cc94cdda077a8df5cd, 61d8658b4a435eac729966cc94cdda077a8df5cd, 61d8658b4a435eac729966cc94cdda077a8df5cd, 61d8658b4a435eac729966cc94cdda077a8df5cdunaffected
LinuxLinux4.11, 0, 5.4.280, 5.10.222, 5.15.163, 6.1.98, 6.6.39, 6.9.9, 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.