How severe is CVE-2010-3904?

CVE-2010-3904 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2010-3904?

Affected package information for CVE-2010-3904 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2010-3904?

Apply the canonical ubuntu linux security patch or hotfix for CVE-2010-3904 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2010-3904 across my infrastructure?

Inventory every canonical ubuntu linux deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2010-3904 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2010-3904?

O3 detects and blocks CVE-2010-3904 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2010-3904 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2010-3904, including 2 documented proof-of-concept exploits on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2010-3904?

CVE-2010-3904 has an EPSS (Exploit Prediction Scoring System) score of 12.2%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2010-3904 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2010-3904 (Linux Kernel Improper Input Validation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-05-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-06-02. The required action was: The impacted product is end-of-life and should be disconnected if still in use. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2010-3904?

CVE-2010-3904 is classified as CWE-1284 (CWE-1284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2010-3904?

CVE-2010-3904 affects canonical ubuntu linux (6 versions, e.g. 6.06, 8.04, 9.04…); linux linux kernel; opensuse opensuse (2 versions, e.g. 11.2, 11.3); redhat enterprise linux (2 versions, e.g. 5.0, 6.0), and 4 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2010-3904?

3 Metasploit modules reference CVE-2010-3904, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2010-3904 published, and has it been updated?

CVE-2010-3904 was published on December 6, 2010 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-05-12 — agencies required to remediate by 2023-06-02

CVE-2010-3904

HIGH

The rds_page_copy_user function in net/rds/page.c in the Reliable Datagram Sockets (RDS) protocol implementation in the Linux kernel before 2.6.36 does not properly validate addresses…

Published

Dec 6, 2010

Updated

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

12.2%probability of exploitation in next 30 days

Moderate Risk96th percentile+0.94%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

The rds_page_copy_user function in net/rds/page.c in the Reliable Datagram Sockets (RDS) protocol implementation in the Linux kernel before 2.6.36 does not properly validate addresses obtained from user space, which allows local users to gain privileges via crafted use of the sendmsg and recvmsg system calls.

Affected Products

8 products · 18 configurations

ubuntu linuxcanonical

6 versions

6.068.049.049.1010.0410.10

linux kernellinux

< 2.6.36

range

opensuseopensuse

2 versions

11.211.3

enterprise linuxredhat

2 versions

5.06.0

linux enterprise desktopsuse

1 version

linux enterprise real time extensionsuse

1 version

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-15285locallinux✓ Verified

Linux Kernel 2.6.36-rc8 - 'RDS Protocol' Local Privilege Escalation

by Dan Rosenberg · Oct 19, 2010

Exploit-DB Source

EDB-44677locallinux✓ Verified

Linux 2.6.30 < 2.6.36-rc8 - Reliable Datagram Sockets (RDS) Privilege Escalation (Metasploit)

by Metasploit · May 21, 2018

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every canonical ubuntu linux deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the canonical ubuntu linux security patch or hotfix for CVE-2010-3904 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2010-3904 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2010-3904. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2010-3904 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2010-3904 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works