Menu

Star on GitHub · 3.2k

CVE-2025-68759

In the Linux kernel, the following vulnerability has been resolved: wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring() In rtl8180_init_rx_ring(), memory is allocated for skb pack…

Published Jan 5, 2026EPSS 0.20%

Overview

CVE-2025-68759 is a known-severity vulnerability. It was published on January 5, 2026.

Technical description

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

wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring()

In rtl8180_init_rx_ring(), memory is allocated for skb packets and DMA

allocations in a loop. When an allocation fails, the previously

successful allocations are not freed on exit.

Fix that by jumping to err_free_rings label on error, which calls

rtl8180_free_rx_ring() to free the allocations. Remove the free of

rx_ring in rtl8180_init_rx_ring() error path, and set the freed

priv->rx_buf entry to null, to avoid double free.

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-2025-68759?

CVE-2025-68759 is a known-severity vulnerability. It was published on January 5, 2026.

How severe is CVE-2025-68759?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-68759?

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-2025-68759?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68759 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.