CVE-2025-30715

What it actually does

High-privileged network attacker can trigger a hang or repeatable crash in the Server: Components Services component, resulting in complete denial of service for the MySQL process.

Why it matters to the business

Database availability is lost until the server is restarted, causing operational downtime for any applications or services that depend on the database; low exploit probability and absence from known exploitation lists reduce immediate urgency, though the large number of downstream package dependents increases exposure scope.

How an attack unfolds

An attacker with high-privileged network credentials connects to the MySQL server over any supported protocol and sends specially crafted requests to the Components Services component; because the flaw is easily exploitable, the server process hangs or crashes repeatedly, achieving denial of service without requiring further authentication bypass.

How to fix it

Upgrade affected MySQL installations to a fixed release; for the listed linux-azure-fde package on Ubuntu 22.04 LTS apply version 5.15.0-1073.82.1 or later. Apply the update during the next maintenance window given the low EPSS and lack of KEV listing.

How to confirm the fix worked

Confirm the installed MySQL version is no longer within the affected ranges (8.0.0-8.0.41, 8.4.0-8.4.4, 9.0.0-9.2.0) and verify the linux-azure-fde package reports 5.15.0-1073.82.1 or newer; test that authenticated high-privileged connections no longer cause process termination.

Typical attack path

1. Obtain high-privileged network credentials for the MySQL instance
2. Establish a connection using any supported protocol
3. Send crafted requests targeting the Components Services component
4. Observe repeated process hang or crash resulting in denial of service

How to detect it

Review database server logs and process monitoring for unexpected restarts or crashes correlated with authenticated connections; examine network traffic for repeated connections from privileged accounts around the time of service interruption.

What your security team should do

• Prioritize patching during the next scheduled maintenance window due to low EPSS and no KEV listing
• Restrict network access to MySQL ports to only trusted sources and enforce least-privilege accounts
• Monitor database process health and restart procedures as compensating controls until patches are deployed