# CVE-2025-22104: ibmvnic: Use kernel helpers for hex dumps

> A buffer overflow in the ibmvnic driver allows out-of-bounds reads, potentially causing system crashes or leaking sensitive memory data.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **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:** 16 Apr 2025
- **Updated:** 2 Sep 2026
- **Also known as:** BELL-CVE-2025-22104, DEBIAN-CVE-2025-22104, GHSA-2q7g-23rp-fjwm, ROOT-OS-DEBIAN-11-CVE-2025-22104, ROOT-OS-DEBIAN-12-CVE-2025-22104, ROOT-OS-DEBIAN-13-CVE-2025-22104, ROOT-OS-UBUNTU-2204-CVE-2025-22104, ROOT-OS-UBUNTU-2404-CVE-2025-22104, UBUNTU-CVE-2025-22104

## What is CVE-2025-22104?

CVE-2025-22104 is a high-severity memory corruption vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ibmvnic: Use kernel helpers for hex dumps

Previously, when the driver was printing hex dumps, the buffer was cast
to an 8 byte long and printed using string formatters. If the buffer
size was not a multiple of 8 then a read buffer overflow was possible.

Therefore, create a new ibmvnic function that loops over a buffer and
calls hex_dump_to_buffer instead.

This patch address KASAN reports like the one below:
  ibmvnic 30000003 env3: Login Buffer:
  ibmvnic 30000003 env3: 01000000af000000
  <...>
  ibmvnic 30000003 env3: 2e6d62692e736261
  ibmvnic 30000003 env3: 65050003006d6f63
  ==================================================================
  BUG: KASAN: slab-out-of-bounds in ibmvnic_login+0xacc/0xffc [ibmvnic]
  Read of size 8 at addr c0000001331a9aa8 by task ip/17681
  <...>
  Allocated by task 17681:
  <...>
  ibmvnic_login+0x2f0/0xffc [ibmvnic]
  ibmvnic_open+0x148/0x308 [ibmvnic]
  __dev_open+0x1ac/0x304
  <...>
  The buggy address is located 168 bytes inside of
                allocated 175-byte region [c0000001331a9a00, c0000001331a9aaf)
  <...>
  =================================================================
  ibmvnic 30000003 env3: 000000000033766e

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-22104?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-22104?

Apply the vendor's patch.

## Is CVE-2025-22104 being exploited?

There is no known exploitation of CVE-2025-22104 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-2025-22104 and fix it if it is affected.

What it is: CVE-2025-22104 is a high-severity memory corruption vulnerability in Linux kernel, published on 16 Apr 2025. 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-2025-22104 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-2025-22104/ (Markdown: https://insights.sbomify.com/CVE-2025-22104/index.md)
```

## Sources

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

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