CVE-2023-52789: tty: vcc: Add check for kstrdup() in vcc_probe()
First published: Tue May 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: tty: vcc: Add check for kstrdup() in vcc_probe() Add check for the return value of kstrdup() and return the error, if it fails in order to avoid NULL pointer dereference.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | <4.14.331 | |
| Linux Kernel | >=4.15<4.19.300 | |
| Linux Kernel | >=4.20<5.4.262 | |
| Linux Kernel | >=5.5<5.10.202 | |
| Linux Kernel | >=5.11<5.15.140 | |
| Linux Kernel | >=5.16<6.1.64 | |
| Linux Kernel | >=6.2<6.5.13 | |
| Linux Kernel | >=6.6<6.6.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/38cd56fc9de78bf3c878790785e8c231116ef9d3
- https://git.kernel.org/stable/c/909963e0c16778cec28efb1affc21558825f4200
- https://git.kernel.org/stable/c/460284dfb10b207980c6f3f7046e33446ceb38ac
- https://git.kernel.org/stable/c/4ef41a7f33ffe1a335e7db7e1564ddc6afad47cc
- https://git.kernel.org/stable/c/6c80f48912b5bd4965352d1a9a989e21743a4a06
- https://git.kernel.org/stable/c/7cebc86481bf16049e266f6774d90f2fd4f8d5d2
- https://git.kernel.org/stable/c/4a24a31826246b15477399febd13292b0c9f0ee9
- https://git.kernel.org/stable/c/8f8771757b130383732195497e47fba2aba76d3a
- https://git.kernel.org/stable/c/d81ffb87aaa75f842cd7aa57091810353755b3e6
Frequently Asked Questions
What is the severity of CVE-2023-52789?
CVE-2023-52789 has a medium severity rating due to its potential for a NULL pointer dereference.
How do I fix CVE-2023-52789?
To fix CVE-2023-52789, update to a patched version of the Linux kernel that addresses the kstrdup() return value check.
Which Linux kernel versions are affected by CVE-2023-52789?
CVE-2023-52789 affects Linux kernel versions up to and including 6.6.3, from versions 4.14 through 6.6.
Is there a workaround for CVE-2023-52789?
There is no specific workaround for CVE-2023-52789; upgrading the kernel is the recommended solution.
What could happen if CVE-2023-52789 is not mitigated?
If CVE-2023-52789 is not mitigated, it could lead to system instability or crashes due to NULL pointer dereferences.
- agent/title
- agent/weakness
- agent/references
- agent/description
- agent/first-publish-date
- agent/type
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/severity
- agent/last-modified-date
- agent/softwarecombine
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/linux
- canonical/linux kernel
- version/linux kernel/4.15
- version/linux kernel/4.20
- version/linux kernel/5.5
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.6