CVE-2023-53394: net/mlx5e: xsk: Fix crash on regular rq reactivation
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: xsk: Fix crash on regular rq reactivation
When the regular rq is reactivated after the XSK socket is closed
it could be reading stale cqes which eventually corrupts the rq.
This leads to no more traffic being received on the regular rq and a
crash on the next close or deactivation of the rq.
Kal Cuttler Conely reported this issue as a crash on the release
path when the xdpsock sample program is stopped (killed) and restarted
in sequence while traffic is running.
This patch flushes all cqes when during the rq flush. The cqe flushing
is done in the reset state of the rq. mlx5e_rq_to_ready code is moved
into the flush function to allow for this.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash networking on affected systems using the mlx5 Ethernet driver with XSK/AF_XDP activity. It is a local denial-of-service risk, not a remote code execution issue based on the provided sources. Business impact is mainly service disruption on hosts running the affected driver and workload.
Executive priority
Handle through normal kernel patch management, with higher priority for performance networking hosts using mlx5 hardware and AF_XDP/XSK. The main risk is outage or degraded network availability, and no provided source supports active exploitation.
Technical view
In net/mlx5e XSK handling, reactivating the regular receive queue after an XSK socket closes can process stale completion queue entries. That can corrupt the receive queue, stop traffic reception, and crash during later queue close or deactivation. CVSS 3.1 is 5.5, local, low complexity, low privileges, availability high.
Likely exposure
Likely exposure is Linux systems using the mlx5 Ethernet driver and XSK/AF_XDP workloads. The CVE record lists affected Linux versions including 6.1, 6.4.10, and 6.5, plus commit identifiers. Exact exposure depends on distribution kernel backports and whether this driver and workload are present.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The reported scenario involved stopping and restarting the xdpsock sample while traffic was running. Treat this as a local availability issue requiring privileges and relevant network-driver usage, not as evidence of broad exploitation.
Researcher notes
Evidence is limited to the CVE record and Linux stable commits. The root cause is stale CQE handling during receive-queue reactivation after XSK socket closure. Avoid over-scoping beyond Linux mlx5e/XSK paths unless vendor advisories map additional affected packages.
Mitigation direction
Apply a Linux kernel update containing the referenced stable fixes.
Check your Linux distribution advisory for backported mlx5e fixes.
Prioritize hosts using mlx5 hardware with AF_XDP or XSK workloads.
Limit local access to users allowed to run XSK-related networking workloads.
Validation and detection
Identify systems running Linux kernels matching the affected versions or commits.
Confirm whether mlx5e driver and XSK or AF_XDP workloads are used.
Check distro kernel changelogs for the referenced stable commit IDs.
Monitor affected hosts for receive-queue stalls or related kernel crashes.
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-53394 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.