LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48758: scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put()

In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() The bnx2fc_destroy() functions are removing the interface before calling destroy_work. This results multiple WARNings from sysfs_remove_group() as the controller rport device attributes are removed too early. Replace the fcoe_port's destroy_work queue. It's not needed. The problem is easily reproducible with the following steps. Example: $ dmesg -w & $ systemctl enable --now fcoe $ fipvlan -s -c ens2f1 $ fcoeadm -d ens2f1.802 [ 583.464488] host2: libfc: Link down on port (7500a1) [ 583.472651] bnx2fc: 7500a1 - rport not created Yet!! [ 583.490468] ------------[ cut here ]------------ [ 583.538725] sysfs group 'power' not found for kobject 'rport-2:0-0' [ 583.568814] WARNING: CPU: 3 PID: 192 at fs/sysfs/group.c:279 sysfs_remove_group+0x6f/0x80 [ 583.607130] Modules linked in: dm_service_time 8021q garp mrp stp llc bnx2fc cnic uio rpcsec_gss_krb5 auth_rpcgss nfsv4 ... [ 583.942994] CPU: 3 PID: 192 Comm: kworker/3:2 Kdump: loaded Not tainted 5.14.0-39.el9.x86_64 #1 [ 583.984105] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013 [ 584.016535] Workqueue: fc_wq_2 fc_rport_final_delete [scsi_transport_fc] [ 584.050691] RIP: 0010:sysfs_remove_group+0x6f/0x80 [ 584.074725] Code: ff 5b 48 89 ef 5d 41 5c e9 ee c0 ff ff 48 89 ef e8 f6 b8 ff ff eb d1 49 8b 14 24 48 8b 33 48 c7 c7 ... [ 584.162586] RSP: 0018:ffffb567c15afdc0 EFLAGS: 00010282 [ 584.188225] RAX: 0000000000000000 RBX: ffffffff8eec4220 RCX: 0000000000000000 [ 584.221053] RDX: ffff8c1586ce84c0 RSI: ffff8c1586cd7cc0 RDI: ffff8c1586cd7cc0 [ 584.255089] RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb567c15afc00 [ 584.287954] R10: ffffb567c15afbf8 R11: ffffffff8fbe7f28 R12: ffff8c1486326400 [ 584.322356] R13: ffff8c1486326480 R14: ffff8c1483a4a000 R15: 0000000000000004 [ 584.355379] FS: 0000000000000000(0000) GS:ffff8c1586cc0000(0000) knlGS:0000000000000000 [ 584.394419] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 584.421123] CR2: 00007fe95a6f7840 CR3: 0000000107674002 CR4: 00000000000606e0 [ 584.454888] Call Trace: [ 584.466108] device_del+0xb2/0x3e0 [ 584.481701] device_unregister+0x13/0x60 [ 584.501306] bsg_unregister_queue+0x5b/0x80 [ 584.522029] bsg_remove_queue+0x1c/0x40 [ 584.541884] fc_rport_final_delete+0xf3/0x1d0 [scsi_transport_fc] [ 584.573823] process_one_work+0x1e3/0x3b0 [ 584.592396] worker_thread+0x50/0x3b0 [ 584.609256] ? rescuer_thread+0x370/0x370 [ 584.628877] kthread+0x149/0x170 [ 584.643673] ? set_kthread_struct+0x40/0x40 [ 584.662909] ret_from_fork+0x22/0x30 [ 584.680002] ---[ end trace 53575ecefa942ece ]---

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects systems using the bnx2fc Fibre Channel over Ethernet driver. During interface teardown, cleanup happens in the wrong order, causing kernel warnings as sysfs device attributes are removed too early. The provided sources do not show data theft, privilege escalation, or active exploitation.

Executive priority

Prioritize in environments that depend on FCoE storage connectivity, because kernel cleanup warnings can indicate operational fragility. For general server fleets without bnx2fc/FCoE, urgency is lower, but kernel patch tracking should still include it.

Technical view

The bnx2fc_destroy() path removes the interface before destroy_work completes. That can trigger WARNings from sysfs_remove_group() when controller rport attributes are deleted prematurely. Kernel stable commits change the teardown behavior by flushing or removing the destroy_work queue before bnx2fc_interface_put().

Likely exposure

Exposure appears limited to Linux systems with affected kernels and the bnx2fc FCoE driver in use. Systems not using Broadcom bnx2fc or Fibre Channel over Ethernet are unlikely to be exposed based on the source bundle.

Exploitation context

The CVE source describes reproducibility during FCoE interface setup and teardown. It does not provide evidence of remote exploitation, public weaponization, or inclusion in CISA KEV. Treat it as an operational kernel stability issue unless vendor guidance says otherwise.

Researcher notes

The affected evidence is specific to bnx2fc teardown ordering. Severity, CVSS, CWE, and exploitability details are not supplied. Avoid broad Linux-impact claims; focus assessment on whether bnx2fc is loaded, FCoE is configured, and vendor kernels include the stable fix.

Mitigation direction

  • Update to a vendor kernel containing the referenced upstream stable fix.
  • Check Linux distribution advisories for backported fixes matching CVE-2022-48758.
  • Disable or avoid bnx2fc/FCoE where it is not operationally required.
  • Plan reboot or maintenance if kernel replacement is needed.
  • Monitor kernel logs for repeated bnx2fc, rport, or sysfs warnings.

Validation and detection

  • Inventory Linux hosts using bnx2fc or Fibre Channel over Ethernet.
  • Map deployed kernel packages to vendor advisories or stable fix commits.
  • Review kernel logs for sysfs_remove_group warnings involving rport objects.
  • After updating, validate FCoE teardown in a non-production test path.
  • Confirm unused FCoE services or drivers remain disabled.
Prepared
Confidence
medium
Sources
11

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-48758 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
10Source 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
LinuxLinux0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978, 0cbf32e1681d870632a1772601cbaadd996dc978unaffected
LinuxLinux3.2, 0, 4.4.302, 4.9.300, 4.14.265, 4.19.228, 5.4.176, 5.10.96, 5.15.19, 5.16.5, 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.