LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53476: iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry()

In the Linux kernel, the following vulnerability has been resolved: iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry() This condition needs to match the previous "if (epcp->state == LISTEN) {" exactly to avoid a NULL dereference of either "listen_ep" or "ep". The problem is that "epcp" has been re-assigned so just testing "if (epcp->state == LISTEN) {" a second time is not sufficient.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53476 is a Linux kernel flaw in the iw_cxgb4 driver. A logic mismatch can lead to a NULL pointer dereference, which may crash affected systems if the vulnerable code path is reached. The public record does not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat as a targeted availability risk for Linux infrastructure using Chelsio iw_cxgb4 functionality. Prioritize patch validation where that driver is present. Broader emergency action is not supported by the current sources because exploitation and severity details are limited.

Technical view

The issue is in c4iw_fill_res_cm_id_entry() in the Linux kernel iw_cxgb4 component. After epcp is reassigned, a later LISTEN-state check no longer exactly matches the earlier condition, risking NULL dereference of listen_ep or ep. Upstream stable fixes are referenced in the CVE record.

Likely exposure

Exposure is most likely on Linux systems using the Chelsio iw_cxgb4 RDMA/iWARP driver. The CVE record lists affected Linux kernel version ranges and fixed stable commits, but distro-specific package status must be confirmed with each vendor.

Exploitation context

CISA KEV is false, and the provided sources do not report active exploitation. The record describes a potential NULL dereference, suggesting availability impact is the main concern. Public sources do not describe attacker prerequisites or remote reachability.

Researcher notes

The CVE text identifies the root cause but does not provide CVSS, CWE, detailed affected distributions, or exploitation prerequisites. Review the four kernel stable commits and downstream distro backports to determine exact exposure for maintained and custom kernels.

Mitigation direction

  • Update affected Linux kernels using vendor packages that include the upstream stable fixes.
  • Prioritize systems using iw_cxgb4 or Chelsio RDMA/iWARP functionality.
  • If no vendor package is available, follow vendor guidance for temporary risk reduction.
  • Track the referenced upstream stable commits when assessing custom kernels.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify systems loading or depending on the iw_cxgb4 driver.
  • Compare running kernels against vendor advisories and fixed upstream stable commits.
  • Confirm remediation by verifying the installed kernel includes the referenced fix.
Prepared
Confidence
medium
Sources
6

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-2023-53476 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
5Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux116aeb8873712ea559d26b0d9d88147af5c88db5, 116aeb8873712ea559d26b0d9d88147af5c88db5, 116aeb8873712ea559d26b0d9d88147af5c88db5, 116aeb8873712ea559d26b0d9d88147af5c88db5unaffected
LinuxLinux4.18, 0, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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