dbcve.org
AndroidOperating system · Google

CVE-2024-47035

HIGH · 7.8 CVSS v3.1 Published 2024-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In vring_init of external/headers/include/virtio/virtio_ring.h, there is a possible out of bounds write due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a kernel-level vulnerability in the virtio virtual device subsystem. The vring_init function in virtio_ring.h contains a logic error causing an out-of-bounds write when initializing virtual ring buffers used for host-guest communication. The flaw can be exploited for local privilege escalation without additional privileges or user interaction.

MitigationApply the vendor patch to fix the logic error in vring_init within the virtio ring header; if no patch exists, review and correct the array bounds checking logic in the affected function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the target device runs Google Android
    Check the OS version by running 'getprop ro.build.version.release' or checking /system/build.prop for 'ro.build.version.sdk'
    Affected if The device is running Google Android (all versions are listed as affected)
  2. Confirm virtio kernel support is present
    Check if the kernel has virtio modules loaded by running 'lsmod | grep virtio' or check /proc/modules for virtio entries; also verify kernel config with 'grep -i virtio /proc/config.gz' or check /boot/config-*
    Affected if Virtio is enabled in the kernel (the vulnerability exists in the virtio vring_init function)
  3. Locate the virtio_ring.h header file
    Find the kernel source or header file typically at /usr/src/linux-headers-*/include/linux/virtio_ring.h or within the kernel source tree under drivers/virtio/
    Affected if The vring_init function in virtio_ring.h contains the vulnerable code
  4. Inspect vring_init function for the logic error
    Review the vring_init function in virtio_ring.h to identify the array bounds checking logic; look for conditions where the index calculation may exceed the allocated buffer size
    Affected if The function has flawed bounds checking that allows out-of-bounds writes during ring buffer initialization
  5. Identify if virtio devices are in use
    Check for active virtio devices by running 'ls -la /sys/bus/virtio/devices/' or checking dmesg output for virtio driver initialization messages
    Affected if Virtio virtual devices (net, block, console, etc.) are instantiated and actively used for host-guest communication

The environment is affected if it is a Google Android device with virtio support enabled and the vulnerable vring_init function in virtio_ring.h is present without the vendor patch applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch to fix the logic error in vring_init within the virtio ring header; if no patch exists, review and correct the array bounds checking logic in the affected function.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47035 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data