CVE-2024-53204

Kernel crash via unchecked PHY allocation

Published Dec 27, 2024 · Updated May 11, 2026

NULL pointer dereference in the Realtek USB 3.0 PHY driver in Linux 6.6 and 6.9 allows local users to crash the kernel. rtk_usb3phy_probe() stores a devm_kzalloc() result in phy_cfg and passes it to memcpy() without checking whether allocation returned NULL. Reaching the fault requires probing a compatible Realtek USB 3.0 PHY while that kernel allocation fails, and the bounded consequence is a kernel crash.

CVSS severity5.5
Medium
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

NULL pointer dereference in the Realtek USB 3.0 PHY driver in Linux 6.6 and 6.9 allows local users to crash the kernel. rtk_usb3phy_probe() stores a devm_kzalloc() result in phy_cfg and passes it to memcpy() without checking whether allocation returned NULL. Reaching the fault requires probing a compatible Realtek USB 3.0 PHY while that kernel allocation fails, and the bounded consequence is a kernel crash.

The record

CVE
CVE-2024-53204
Published
Dec 27, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-476, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 27, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.6
  2. Affected versionversion=6.9
  3. Affected versionversion=adda6e82a7de7d6d478f6c8ef127f0ac51c510a1 <258ea41c926b7b3a16d0d7aa210a1401c4a1601b
  4. Affected versionversion=adda6e82a7de7d6d478f6c8ef127f0ac51c510a1 <e27877990e54bfe4246dd850f7ec8646c999ce58
  5. Affected versionversion=b48415afe5fd7e6f5912d4c45720217b77d8e7ea <48d52d3168749e10c1c37cd4ceccd18625851741
  6. Affected versionversion=b48415afe5fd7e6f5912d4c45720217b77d8e7ea <776f13ad1f88485206f1dca5ef138553106950e5
  7. Affected versionversion=b48415afe5fd7e6f5912d4c45720217b77d8e7ea <bf373d2919d98f3d1fe1b19a0304f72fe74386d9

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.6; version=6.9; version=adda6e82a7de7d6d478f6c8ef127f0ac51c510a1 <258ea41c926b7b3a16d0d7aa210a1401c4a1601b; version=adda6e82a7de7d6d478f6c8ef127f0ac51c510a1 <e27877990e54bfe4246dd850f7ec8646c999ce58; version=b48415afe5fd7e6f5912d4c45720217b77d8e7ea <48d52d3168749e10c1c37cd4ceccd18625851741; version=b48415afe5fd7e6f5912d4c45720217b77d8e7ea <776f13ad1f88485206f1dca5ef138553106950e5; version=b48415afe5fd7e6f5912d4c45720217b77d8e7ea <bf373d2919d98f3d1fe1b19a0304f72fe74386d9

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-476NULL Pointer Dereference
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo