Stack-based Buffer Overflow Affecting kernel-debuginfo-common-x86_64 package, versions <0:4.14.349-266.564.amzn2

Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo-common-x86_64 package and not the kernel-debuginfo-common-x86_64 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:

kdb: Fix buffer overflow during tab-complete

Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer rather than the destination to strncpy() with predictably horrible results. Most obviously if the command buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write past the end of the supplied buffer.

Fix this by replacing the dubious strncpy() calls with memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start moving characters around.

• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39480
• https://git.kernel.org/stable/c/107e825cc448b7834b31e8b1b3cf0f57426d46d5
• https://git.kernel.org/stable/c/33d9c814652b971461d1e30bead6792851c209e7
• https://git.kernel.org/stable/c/cfdc2fa4db57503bc6d3817240547c8ddc55fa96
• https://git.kernel.org/stable/c/ddd2972d8e2dee3b33e8121669d55def59f0be8a
• https://git.kernel.org/stable/c/e9730744bf3af04cda23799029342aa3cddbc454
• https://git.kernel.org/stable/c/f636a40834d22e5e3fc748f060211879c056cd33
• https://git.kernel.org/stable/c/f694da720dcf795dc3eb97bf76d220213f76aaa7
• https://git.kernel.org/stable/c/fb824a99e148ff272a53d71d84122728b5f00992