LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54156: sfc: fix crash when reading stats while NIC is resetting

In the Linux kernel, the following vulnerability has been resolved: sfc: fix crash when reading stats while NIC is resetting efx_net_stats() (.ndo_get_stats64) can be called during an ethtool selftest, during which time nic_data->mc_stats is NULL as the NIC has been fini'd. In this case do not attempt to fetch the latest stats from the hardware, else we will crash on a NULL dereference: BUG: kernel NULL pointer dereference, address: 0000000000000038 RIP efx_nic_update_stats abridged calltrace: efx_ef10_update_stats_pf efx_net_stats dev_get_stats dev_seq_printf_stats Skipping the read is safe, we will simply give out stale stats. To ensure that the free in efx_ef10_fini_nic() does not race against efx_ef10_update_stats_pf(), which could cause a TOCTTOU bug, take the efx->stats_lock in fini_nic (it is already held across update_stats).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system when network statistics are read while an sfc NIC is resetting. The source describes a NULL pointer dereference, not data theft or code execution. Business urgency depends on whether affected Linux kernels and sfc-supported NICs are in use.

Executive priority

Treat as targeted availability risk, not broad emergency, unless critical Linux hosts use affected sfc NICs. Patch through normal kernel maintenance, with higher priority for systems where network resets or diagnostics are common.

Technical view

The sfc driver’s efx_net_stats path may call hardware stats update while nic_data->mc_stats is NULL during ethtool selftest or NIC finalization. The fix skips hardware stat refresh in that state and locks fini_nic against update_stats to avoid a race.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the sfc network driver/NIC path. The bundle lists Linux as affected and names versions including 5.9, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, and 6.5.

Exploitation context

The bundle reports no KEV listing, no CVSS, and no active exploitation evidence. The described trigger is reading network statistics during NIC reset or ethtool selftest, leading to kernel crash behavior rather than confirmed attacker-controlled compromise.

Researcher notes

Key evidence is the kernel fix description: mc_stats can be NULL during selftest/fini, and locking was added to prevent a TOCTTOU race. Sources do not provide exploitability, attacker prerequisites, or remote reachability.

Mitigation direction

  • Upgrade to a Linux kernel containing the referenced stable fix commits.
  • Check distribution advisories for backported fixes for CVE-2023-54156.
  • Prioritize hosts using the sfc driver or affected NIC hardware.
  • Avoid unnecessary ethtool selftests during NIC reset windows until patched.

Validation and detection

  • Inventory Linux kernel versions against the affected version list in the CVE record.
  • Identify systems loading or packaging the sfc network driver.
  • Confirm the installed kernel includes one referenced stable commit or distro backport.
  • Review crash logs for efx_nic_update_stats or efx_net_stats NULL dereferences.
Prepared
Confidence
medium
Sources
8

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-2023-54156 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
0ADP providers
7Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd3142c193dca9a2f6878f4128ce1aaf221bb3f99, d3142c193dca9a2f6878f4128ce1aaf221bb3f99, d3142c193dca9a2f6878f4128ce1aaf221bb3f99, d3142c193dca9a2f6878f4128ce1aaf221bb3f99, d3142c193dca9a2f6878f4128ce1aaf221bb3f99, d3142c193dca9a2f6878f4128ce1aaf221bb3f99unaffected
LinuxLinux5.9, 0, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

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