CVE-2024-43701
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 · uneditedSoftware installed and run as a non-privileged user may conduct GPU system calls to read and write freed physical memory from the GPU.
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 confidenceA use-after-free vulnerability in GPU memory management allows non-privileged users to make GPU system calls that can read and write to freed physical memory, potentially enabling privilege escalation or information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GPU drivers or softwareRun system commands to list GPU drivers: on Linux 'lsmod | grep -i gpu' or 'lspci | grep -i vga', on Windows check Device Manager under Display adaptersAffected if Any GPU driver or related software is installed without knowing the exact version status
-
Determine the exact version of the GPU driverUse vendor-specific commands: NVIDIA 'nvidia-smi', AMD 'amdgpu-version' or 'rocm-smi', Intel 'intel_gpu_top' or check driver files in /usr/lib/x86_64-linux-gnu/ (Linux) or driver properties (Windows)Affected if The installed version is unknown or falls within any unpatched version range for this vulnerability
-
Verify if non-privileged user GPU access is permittedCheck user group membership for video/GPU groups (video, render, wheel on Linux) and review /dev/dri/* permissions, or on Windows check if non-admin users can access GPU device APIsAffected if Non-privileged users have direct access to GPU system calls or device nodes without restrictions
-
Inspect GPU memory management configurationReview GPU driver configuration files and runtime settings: check /etc/X11/xorg.conf (Linux), NVIDIA Control Panel settings, or AMD Radeon settings for memory allocation policiesAffected if Memory isolation settings are disabled or set to allow unsafe memory operations
-
Check for recent GPU driver updates or patchesQuery the vendor's security bulletin or patch notes for CVE-2024-43701, and check system logs for recent driver updatesAffected if No patch for this specific CVE has been applied to the installed GPU software
The environment is affected if any GPU driver or related software is installed and non-privileged users can access GPU system calls without having received the vendor patch for this use-after-free vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided patches for affected GPU drivers/software and ensure proper memory isolation is enforced in GPU operations.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43701 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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