CVE-2025-68759

Kernel memory leak via failed RX allocation

Published Jan 5, 2026 · Updated Jan 5, 2026

Memory leak in the Linux Kernel rtl8180 driver allows attackers to retain kernel memory through failed RX-ring allocation. The rtl8180_init_rx_ring() error path exits after an skb or DMA allocation failure without releasing allocations completed earlier in the loop. Exposure requires the rtl8180 driver and a receive-ring allocation failure during device initialization; the published record identifies no attacker-controlled trigger or impact beyond retained kernel memory.

CVSS severity0.0
None
EPSS probability0.19%
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

Memory leak in the Linux Kernel rtl8180 driver allows attackers to retain kernel memory through failed RX-ring allocation. The rtl8180_init_rx_ring() error path exits after an skb or DMA allocation failure without releasing allocations completed earlier in the loop. Exposure requires the rtl8180 driver and a receive-ring allocation failure during device initialization; the published record identifies no attacker-controlled trigger or impact beyond retained kernel memory.

The record

CVE
CVE-2025-68759
Published
Jan 5, 2026
Updated
Jan 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 5, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 5, 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=2.6.25
  2. Affected versionversion=f653211197f3841f383fa9757ef8ce182c6cf627 <9b5b9c042b30befc5b37e4539ace95af70843473
  3. Affected versionversion=f653211197f3841f383fa9757ef8ce182c6cf627 <a813a74570212cb5f3a7d3b05c0cb0cd00bace1d
  4. Affected versionversion=f653211197f3841f383fa9757ef8ce182c6cf627 <c9d1c4152e6d32fa74034464854bee262a60bc43
  5. Affected versionversion=f653211197f3841f383fa9757ef8ce182c6cf627 <ee7db11742b30641f21306105ad27a275e3c61d7

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=2.6.25; version=f653211197f3841f383fa9757ef8ce182c6cf627 <9b5b9c042b30befc5b37e4539ace95af70843473; version=f653211197f3841f383fa9757ef8ce182c6cf627 <a813a74570212cb5f3a7d3b05c0cb0cd00bace1d; version=f653211197f3841f383fa9757ef8ce182c6cf627 <c9d1c4152e6d32fa74034464854bee262a60bc43; version=f653211197f3841f383fa9757ef8ce182c6cf627 <ee7db11742b30641f21306105ad27a275e3c61d7

Published CVSS scores

0.0Oracle LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N

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

No sourced classifications are available.

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