Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-48627, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 80% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 81732c3b2fede049a692e58a7ceabb6d18ffb18c – < c8686c014b5e872ba7e334f33ca553f14446fc29
    • affected 81732c3b2fede049a692e58a7ceabb6d18ffb18c – < 815be99d934e3292906536275f2b8d5131cdf52c
    • affected 81732c3b2fede049a692e58a7ceabb6d18ffb18c – < bfee93c9a6c395f9aa62268f1cedf64999844926
    • affected 81732c3b2fede049a692e58a7ceabb6d18ffb18c – < 57964a5710252bc82fe22d9fa98c180c58c20244
    • affected 81732c3b2fede049a692e58a7ceabb6d18ffb18c – < 14d2cc21ca622310babf373e3a8f0b40acfe8265
    • affected 81732c3b2fede049a692e58a7ceabb6d18ffb18c – < 39cdb68c64d84e71a4a717000b6e5de208ee60cc
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 4.19.312 – ≤ 4.19.*
    • unaffected 5.4.274 – ≤ 5.4.*
    • unaffected 5.10.132 – ≤ 5.10.*
    • unaffected 5.15.56 – ≤ 5.15.*
    • unaffected 5.18.13 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48627 badge
[![CVE-2022-48627](https://cveledger.app/badge/CVE-2022-48627.svg)](https://cveledger.app/cve/CVE-2022-48627)

Record last updated .