kdb: Fix buffer overflow during tab-complete
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.35
References 8
git.kernel.org
- stable/c/fb824a99e148ff272a53d71d84122728b5f00992
- stable/c/ddd2972d8e2dee3b33e8121669d55def59f0be8a
- stable/c/cfdc2fa4db57503bc6d3817240547c8ddc55fa96
- stable/c/f636a40834d22e5e3fc748f060211879c056cd33
- stable/c/33d9c814652b971461d1e30bead6792851c209e7
- stable/c/107e825cc448b7834b31e8b1b3cf0f57426d46d5
- stable/c/f694da720dcf795dc3eb97bf76d220213f76aaa7
- stable/c/e9730744bf3af04cda23799029342aa3cddbc454