# CVE-2022-2308: Information disclosure in Linux kernel

> A flaw in the Linux kernel VDUSE driver allows uninitialized memory leaks, potentially exposing sensitive data to local attackers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-2308, GHSA-6q37-hh76-6rv4, UBUNTU-CVE-2022-2308, openSUSE-SU-2024:12320-1

## What is CVE-2022-2308?

CVE-2022-2308 is a medium-severity vulnerability in Linux kernel, published on 1 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A 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.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-457 (Use of Uninitialized Variable)

## Which versions are affected by CVE-2022-2308?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-source` | openSUSE:Tumbleweed | All versions | 5.19.8-1.1 |

Products: Linux kernel.

## How do I fix CVE-2022-2308?

Apply the vendor's patch.

## Is CVE-2022-2308 being exploited?

There is no known exploitation of CVE-2022-2308 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2308 and fix it if it is affected.

What it is: CVE-2022-2308 is a medium-severity vulnerability in Linux kernel, published on 1 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2308 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2308/ (Markdown: https://insights.sbomify.com/CVE-2022-2308/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2308
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2308
- OSV: https://osv.dev/vulnerability/CVE-2022-2308

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2308/
Summaries are generated and may contain mistakes; the official description above is the record.