Improper Handling of Overlap Between Protected Memory Ranges Affecting kernel-debuginfo package, versions <0:4.14.345-262.561.amzn2
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-AMZN2-KERNELDEBUGINFO-7681850
- published 14 Aug 2024
- disclosed 2 Mar 2024
Introduced: 2 Mar 2024
CVE-2022-48627 Open this link in a new tabHow to fix?
Upgrade Amazon-Linux:2
kernel-debuginfo
to version 0:4.14.345-262.561.amzn2 or higher.
This issue was patched in ALAS2-2024-2615
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo
package and not the kernel-debuginfo
package as distributed by Amazon-Linux
.
See How to fix?
for Amazon-Linux:2
relevant fixed versions and status.
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.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48627
- https://git.kernel.org/stable/c/14d2cc21ca622310babf373e3a8f0b40acfe8265
- https://git.kernel.org/stable/c/39cdb68c64d84e71a4a717000b6e5de208ee60cc
- https://git.kernel.org/stable/c/57964a5710252bc82fe22d9fa98c180c58c20244
- https://git.kernel.org/stable/c/bfee93c9a6c395f9aa62268f1cedf64999844926
- https://git.kernel.org/stable/c/815be99d934e3292906536275f2b8d5131cdf52c
- https://git.kernel.org/stable/c/c8686c014b5e872ba7e334f33ca553f14446fc29
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html