LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48715: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe

In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe Running tests with a debug kernel shows that bnx2fc_recv_frame() is modifying the per_cpu lport stats counters in a non-mpsafe way. Just boot a debug kernel and run the bnx2fc driver with the hardware enabled. [ 1391.699147] BUG: using smp_processor_id() in preemptible [00000000] code: bnx2fc_ [ 1391.699160] caller is bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [ 1391.699174] CPU: 2 PID: 4355 Comm: bnx2fc_l2_threa Kdump: loaded Tainted: G B [ 1391.699180] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013 [ 1391.699183] Call Trace: [ 1391.699188] dump_stack_lvl+0x57/0x7d [ 1391.699198] check_preemption_disabled+0xc8/0xd0 [ 1391.699205] bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [ 1391.699215] ? do_raw_spin_trylock+0xb5/0x180 [ 1391.699221] ? bnx2fc_npiv_create_vports.isra.0+0x4e0/0x4e0 [bnx2fc] [ 1391.699229] ? bnx2fc_l2_rcv_thread+0xb7/0x3a0 [bnx2fc] [ 1391.699240] bnx2fc_l2_rcv_thread+0x1af/0x3a0 [bnx2fc] [ 1391.699250] ? bnx2fc_ulp_init+0xc0/0xc0 [bnx2fc] [ 1391.699258] kthread+0x364/0x420 [ 1391.699263] ? _raw_spin_unlock_irq+0x24/0x50 [ 1391.699268] ? set_kthread_struct+0x100/0x100 [ 1391.699273] ret_from_fork+0x22/0x30 Restore the old get_cpu/put_cpu code with some modifications to reduce the size of the critical section.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-48715 is a Linux kernel driver issue in bnx2fc, used in some Fibre Channel over Ethernet storage setups. The bug involves unsafe CPU-specific statistics handling and was found during debug-kernel testing. Business urgency is mainly for Linux servers using this driver and hardware; there is no cited evidence of active exploitation.

Executive priority

Treat as a targeted infrastructure maintenance item, not an internet-wide emergency. Prioritize patching servers that depend on bnx2fc-connected storage because instability there could affect availability.

Technical view

bnx2fc_recv_frame() modified per-CPU lport statistics in a non-multiprocessor-safe way, triggering a kernel BUG about smp_processor_id() use in preemptible code. The kernel fix restores get_cpu/put_cpu handling with a smaller critical section. Public records list multiple stable kernel commit references for remediation.

Likely exposure

Exposure appears limited to Linux systems running the bnx2fc driver with supporting hardware enabled. General Linux systems not using this driver are less likely to be exposed. The source lists affected Linux kernel versions, but distribution-specific backports must be checked separately.

Exploitation context

The cited description shows discovery through testing with a debug kernel and enabled hardware. No KEV entry is present, and the provided sources do not claim active exploitation or provide a remote attack path.

Researcher notes

Evidence is limited to the kernel CVE record and stable commit references. No CVSS, CWE, exploit status, or distribution-specific package mapping is provided. Validate exposure through actual driver use, not Linux presence alone.

Mitigation direction

  • Identify Linux systems using the bnx2fc driver and related storage hardware.
  • Apply a vendor or distribution kernel update containing the referenced stable fixes.
  • If unsure, consult Linux distribution advisories for CVE-2022-48715 coverage.
  • Prioritize storage hosts where driver instability could affect business services.

Validation and detection

  • Confirm whether the bnx2fc module is present, loaded, or required.
  • Record kernel versions on systems using bnx2fc.
  • Check distribution changelogs for CVE-2022-48715 or the referenced kernel commits.
  • Review kernel logs for related bnx2fc BUG or preemption warnings.
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-2022-48715 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
LinuxLinuxd576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2unaffected
LinuxLinux3.16, 0, 4.9.300, 4.14.265, 4.19.228, 5.4.178, 5.10.99, 5.15.22, 5.16.8, 5.17affected
Weakness

CWE details

No CWE listed

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