CVE-2023-54065
Out-of-Bounds Access in Linux Kernel Realtek DSA Driver
Publication date: 2025-12-24
Last updated on: 2025-12-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| realtek | realtek_kernel_driver | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an out-of-bounds memory access in the Linux kernel's Realtek network driver. Specifically, the probe function incorrectly sets a pointer (priv->chip_data) assuming there is enough allocated space after the priv structure, but this space is only allocated in one variant (realtek-smi) and not in realtek-mdio. This leads to accessing memory beyond the allocated buffer, which can cause memory corruption. The issue was masked previously due to overallocation caused by a large unused buffer, but it becomes apparent with different memory allocators or debugging tools like KASAN.
How can this vulnerability impact me? :
This vulnerability can lead to memory corruption in the Linux kernel when using the affected Realtek network driver. Memory corruption can cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges if exploited. The impact depends on the environment and whether the vulnerable driver is in use.
What immediate steps should I take to mitigate this vulnerability?
Update the Linux kernel to a version where the realtek-mdio driver has been fixed to allocate chip_data space properly, similar to realtek-smi, to prevent out-of-bounds memory access. Avoid using kernel configurations or environments that expose this vulnerability, such as those with different allocators or KASAN enabled, until patched.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by enabling Kernel Address Sanitizer (KASAN) to identify out-of-bounds memory accesses in the realtek-mdio driver. Since the issue involves out-of-bounds access in kernel memory, running the kernel with KASAN enabled can reveal memory corruption related to this flaw. There are no specific network commands to detect this vulnerability directly. To enable KASAN, you can configure your kernel with CONFIG_KASAN=y and reboot. Then, monitor dmesg or kernel logs for KASAN reports indicating out-of-bounds accesses in the realtek-mdio driver.