# CVE-2022-48627: vt: fix memory overlapping when deleting chars in the buffer

> A memory overlapping copy in the Linux kernel VT subsystem can cause data corruption or system instability when deleting long lines.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Mar 2024
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-48627, GHSA-73f5-wqmw-37vp, UBUNTU-CVE-2022-48627

## What is CVE-2022-48627?

CVE-2022-48627 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 2 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

vt: fix memory overlapping when deleting chars in the buffer

A memory overlapping copy occurs when deleting a long line. This memory
overlapping copy can cause data corruption when scr_memcpyw is optimized
to memcpy because memcpy does not ensure its behavior if the destination
buffer overlaps with the source buffer. The line buffer is not always
broken, because the memcpy utilizes the hardware acceleration, whose
result is not deterministic.

Fix this problem by using replacing the scr_memcpyw with scr_memmovew.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2022-48627 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48627 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 2 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-48627 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-48627/ (Markdown: https://insights.sbomify.com/CVE-2022-48627/index.md)
```

## Sources

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

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