Menu

Star on GitHub · 3.2k

CVE-2023-53509

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: qed: allow sleep in qed_mcp_trace_dump() By default, qed_mcp_cmd_and_union() delays 10us at a time in a loop that can run 500K…

Published Oct 1, 2025EPSS 0.15%

Overview

CVE-2023-53509 is a medium-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

qed: allow sleep in qed_mcp_trace_dump()

By default, qed_mcp_cmd_and_union() delays 10us at a time in a loop

that can run 500K times, so calls to qed_mcp_nvm_rd_cmd()

may block the current thread for over 5s.

We observed thread scheduling delays over 700ms in production,

with stacktraces pointing to this code as the culprit.

qed_mcp_trace_dump() is called from ethtool, so sleeping is permitted.

It already can sleep in qed_mcp_halt(), which calls qed_mcp_cmd().

Add a "can sleep" parameter to qed_find_nvram_image() and

qed_nvram_read() so they can sleep during qed_mcp_trace_dump().

qed_mcp_trace_get_meta_info() and qed_mcp_trace_read_meta(),

called only by qed_mcp_trace_dump(), allow these functions to sleep.

I can't tell if the other caller (qed_grc_dump_mcp_hw_dump()) can sleep,

so keep b_can_sleep set to false when it calls these functions.

An example stacktrace from a custom warning we added to the kernel

showing

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2023-53509?

CVE-2023-53509 is a medium-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2023-53509?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-53509?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-53509?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-53509 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2023

View all