CVE-2022-48627
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in, but needs a user to act. High risk of service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-787 · Out-of-bounds write
- Record status
- Analyzed
Affected
- Linux Kernel ≤ 4.19.312
- Linux Kernel < 5.4.274
- Linux Kernel < 5.10.132
- Linux Kernel < 5.15.56
- Linux Kernel < 5.18.13
- Linux Kernel 5.19
- Debian Linux 10.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-48627.md and follow it. Check whether this project is affected by CVE-2022-48627. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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/815be99d934e3292906536275f2b8d5131cdf52c
- https://git.kernel.org/stable/c/bfee93c9a6c395f9aa62268f1cedf64999844926
- https://git.kernel.org/stable/c/c8686c014b5e872ba7e334f33ca553f14446fc29
- 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/815be99d934e3292906536275f2b8d5131cdf52c
References
- 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/815be99d934e3292906536275f2b8d5131cdf52c
- https://git.kernel.org/stable/c/bfee93c9a6c395f9aa62268f1cedf64999844926
- https://git.kernel.org/stable/c/c8686c014b5e872ba7e334f33ca553f14446fc29
- 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/815be99d934e3292906536275f2b8d5131cdf52c
- https://git.kernel.org/stable/c/bfee93c9a6c395f9aa62268f1cedf64999844926
- https://git.kernel.org/stable/c/c8686c014b5e872ba7e334f33ca553f14446fc29
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html