How severe is GHSA-3qx8-rv27-j6gp?

No CVSS score has been assigned to GHSA-3qx8-rv27-j6gp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3qx8-rv27-j6gp?

GHSA-3qx8-rv27-j6gp affects the following packages: kvm-ioctls (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-3qx8-rv27-j6gp?

Update kvm-ioctls to 0.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3qx8-rv27-j6gp is resolved across your whole dependency graph.

How do I detect GHSA-3qx8-rv27-j6gp in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kvm-ioctls, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3qx8-rv27-j6gp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3qx8-rv27-j6gp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3qx8-rv27-j6gp can be triaged on real exposure rather than presence alone.

Is GHSA-3qx8-rv27-j6gp actively exploited in the wild?

No public exploit code has been indexed for GHSA-3qx8-rv27-j6gp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-3qx8-rv27-j6gp published, and has it been updated?

GHSA-3qx8-rv27-j6gp was published on December 23, 2024 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-3qx8-rv27-j6gp — kvm-ioctls

Fix: rust-vmm/kvm#298

GHSA-3qx8-rv27-j6gp is a security vulnerability in kvm-ioctls. A fix is available for kvm-ioctls — see the affected versions and patch details below.

Undefined behaviour in `kvm_ioctls::ioctls::vm::VmFd::create_device`

Also known asRUSTSEC-2024-0428

Published

Dec 23, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀kvm-ioctls

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

An issue was identified in the VmFd::create_device function, leading to undefined behavior and miscompilations on rustc 1.82.0 and newer due to the function's violation of Rust's pointer safety rules.

The function downcasted a mutable reference to its struct kvm_create_device argument to an immutable pointer, and then proceeded to pass this pointer to a mutating system call. Rustc 1.82.0 and newer elides subsequent reads of this structure's fields, meaning code will not see the value written by the kernel into the fd member. Instead, the code will observe the value that this field was initialized to prior to calling VmFd::create_device (usually, 0).

The issue started in kvm-ioctls 0.1.0 and was fixed in 0.19.1 by correctly using a mutable pointer.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`kvm-ioctls`	all versions	0.19.1`cargo update -p kvm-ioctls --precise 0.19.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kvm-ioctls, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kvm-ioctls to 0.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3qx8-rv27-j6gp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3qx8-rv27-j6gp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3qx8-rv27-j6gp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was identified in the `VmFd::create_device function`, leading to undefined behavior and miscompilations on rustc 1.82.0 and newer due to the function's violation of Rust's pointer safety rules. The function downcasted a mutable reference to its `struct kvm_create_device` argument to an immutable pointer, and then proceeded to pass this pointer to a mutating system call. Rustc 1.82.0 and newer elides subsequent reads of this structure's fields, meaning code will not see the value written by the kernel into the `fd` member. Instead, the code will observe the value that this field was i

O3 Security · Impact-Aware SCA

Is GHSA-3qx8-rv27-j6gp in your dependencies?

O3 Security finds GHSA-3qx8-rv27-j6gp across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works