Memory Leak in Error Handling Path in tty: serial: 8250: serial_cs
Summary
GSD-2021-1001481: tty: serial: 8250: serial_cs: Fix a memory leak in error handling path. Affects Kernel versions < b5a2799cd62ed30c81b22c23028d9ee374e2138c. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The tty: serial: 8250: serial_cs package is a component of the Linux Kernel, which is responsible for managing serial communication devices. It provides support for serial ports and allows data transmission between devices. The 8250 driver is a common driver used for serial communication on various platforms. However, a vulnerability has been discovered in the error handling path of the 8250 driver, leading to a memory leak.
Vulnerability Detail
The vulnerability in the tty: serial: 8250: serial_cs package occurs in the error handling path. When an error is encountered during the execution of the driver, a memory leak can occur. This can result in the consumption of excessive memory resources, leading to system instability and potential denial-of-service attacks. The vulnerability has been identified and fixed in Linux Kernel version v4.4.276 by commit b5a2799cd62ed30c81b22c23028d9ee374e2138c.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. The recommended approach is to update the Linux Kernel to the fixed version.
Conclusion
The memory leak vulnerability in the tty: serial: 8250: serial_cs package can lead to system instability and potential denial-of-service attacks. It is crucial to update the Linux Kernel to version v4.4.276 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, causing excessive consumption of memory resources. This can result in system instability and potential denial-of-service attacks.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, the vulnerability has been fixed in Linux Kernel version v4.4.276 by commit b5a2799cd62ed30c81b22c23028d9ee374e2138c. Updating to this version will patch the vulnerability.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to prevent any potential attacks.
You can find more information about this vulnerability in the GSD-2021-1001481.json file available in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001481.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.