Linux KernelOperating system · Linux
CVE-2022-2308
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 · uneditedA flaw was found in vDPA with VDUSE backend. There are currently no checks in VDUSE kernel driver to ensure the size of the device config space is in line with the features advertised by the VDUSE userspace application. In case of a mismatch, Virtio drivers config read helpers do not initialize the memory indirectly passed to vduse_vdpa_get_config() returning uninitialized memory from the stack. This could cause undefined behavior or data leaks in Virtio drivers.
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 · high confidenceA vulnerability exists in the Linux kernel's VDUSE (vDPA Userspace Software) driver where missing validation allows a mismatch between the device config space size and features advertised by the VDUSE userspace application. When Virtio drivers call vduse_vdpa_get_config() to read device configuration, uninitialized stack memory is returned due to improperly initialized buffers, causing potential data leakage or undefined behavior in Virtio drivers.
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
Linux KernelOperating system
all versionsCVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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.
-
Verify VDUSE kernel support is enabledCheck kernel configuration for CONFIG_VDPA or CONFIG_VDPA_USER (e.g., 'grep -E "CONFIG_VDPA|CONFIG_VDPA_USER" /boot/config-$(uname -r)' or check /proc/config.gz')Affected if CONFIG_VDPA or CONFIG_VDPA_USER is set to y or m, indicating the VDUSE driver is available
-
Check if VDUSE module is loadedRun 'lsmod | grep vdpa' or check /sys/module/ for vdpa-related modulesAffected if The vdpa, vdpa_user, or virtio_vdpa module is loaded
-
Identify active VDUSE devicesList /sys/bus/vdpa/devices/ or check for vduse* device nodes in /dev/Affected if Any VDUSE devices are enumerated or present on the system
-
Verify kernel version statusCompare installed kernel version to the version that received the fix (check your distribution's security advisories or kernel.org for CVE-2022-2308 patch availability)Affected if The running kernel version predates the CVE-2022-2308 fix and VDUSE is in use
A system is affected if it has VDUSE support enabled or loaded AND is running a kernel version that predates the CVE-2022-2308 fix, with active VDUSE devices in use.
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 kernel patches that add bounds checking to validate config space size against advertised features before copying data to the vduse_vdpa_get_config() buffer, ensuring all memory is properly initialized.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2308 — 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-2022-2308 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