CVE-2022-48627
MediumIn 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.
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Weakness type
CWE-787CVE-2022-48627 is a Out-of-bounds Write vulnerability
What is Out-of-bounds Write?
The product writes data past the end or before the beginning of the intended buffer. Learn more on MITRE CWE
Affected versions
Linux kernel versions
3.7
and later are affected. Fixed in
4.19.312,
5.4.274,
5.10.132,
5.15.56,
5.18.13,
5.19
and their respective stable series.
References
7 total-
Patch
-
Patch
-
Patch
-
Patch
-
Patch
Frequently asked questions
-
What is CVE-2022-48627?
CVE-2022-48627 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Out-of-bounds Write flaw (CWE-787) . It affects Linux kernel versions from 3.7 onward and has been patched in 4.19.312, 5.4.274, 5.10.132 and others. CVE-2022-48627 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2022-48627?
CVE-2022-48627 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2022-48627?
Yes. CVE-2022-48627 has been patched. Fixed versions include 4.19.312, 5.4.274, 5.10.132 and others. If you are running Linux kernel 3.7 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2022-48627 actively exploited?
No. CVE-2022-48627 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.