How severe is CVE-2011-1823?

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

Which products are affected by CVE-2011-1823?

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

How do I patch CVE-2011-1823?

Apply the google android security patch or hotfix for CVE-2011-1823 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2011-1823 across my infrastructure?

Inventory every google android 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 remote code execution 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-2011-1823 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-2011-1823?

O3 detects and blocks CVE-2011-1823 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-2011-1823 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2011-1823, including 3 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-2011-1823?

CVE-2011-1823 has an EPSS (Exploit Prediction Scoring System) score of 41.6%, placing it in the 99th 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-2011-1823 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2011-1823 (Android OS Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-09-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-09-29. The required action was: Apply updates per vendor instructions. 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-2011-1823?

CVE-2011-1823 is classified as CWE-190 (CWE-190). 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-2011-1823?

CVE-2011-1823 affects google android (1 version, e.g. 3.0). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2011-1823 published, and has it been updated?

CVE-2011-1823 was published on June 9, 2011 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 2022-09-08 — agencies required to remediate by 2022-09-29

CVE-2011-1823

HIGH

The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trusts messages that are received from a PF_NETLINK socket, which allows local users to execute arbitrary code and…

Published

Jun 9, 2011

Updated

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

41.6%probability of exploitation in next 30 days

High Risk99th percentile0.00%

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 vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trusts messages that are received from a PF_NETLINK socket, which allows local users to execute arbitrary code and gain root privileges via a negative index that bypasses a maximum-only signed integer check in the DirectVolume::handlePartitionAdded method, which triggers memory corruption, as demonstrated by Gingerbreak.

Affected Products

1 product · 2 configurations

androidgoogle

≥ 2.0 && < 2.3.4

1 version

3.0

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.

The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trust…

forum.xda-developers.comNVDAug 2017

The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trust…

xorl.wordpress.comNVDAug 2017

The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trust…

c-skills.blogspot.comNVDAug 2017

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every google android 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 remote code execution 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 google android security patch or hotfix for CVE-2011-1823 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-2011-1823 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-2011-1823. 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-2011-1823 being exploited in your environment?

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

Protect my workloads How runtime protection works

CVE-2011-1823

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2011-1823 being exploited in your environment?