Linux Kernel up to 5.15.99/6.1.17/6.2.4 hd44780_remove memory leak

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 5.15.99/6.1.17/6.2.4. The affected element is the function hd44780_remove. Such manipulation leads to memory leak. This vulnerability is listed as CVE-2022-50830. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.15.99/6.1.17/6.2.4 and classified as critical. Affected by this issue is the function hd44780_remove. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: auxdisplay: hd44780: Fix potential memory leak in hd44780_remove() hd44780_probe() allocates a memory chunk for hd with kzalloc() and makes "lcd->drvdata->hd44780" point to it. When we call hd44780_remove(), we should release all relevant memory and resource. But "lcd->drvdata ->hd44780" is not released, which will lead to a memory leak. We should release the "lcd->drvdata->hd44780" in hd44780_remove() to fix the memory leak bug.

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2022-50830 since 12/30/2025. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 281727 (Linux Distros Unpatched Vulnerability : CVE-2022-50830), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.15.100, 6.1.18 or 6.2.5 eliminates this vulnerability. Applying the patch 8311961a1724bfc64390c539dedc31e067a80315/6cd37f8232f5e169a723e1d5fbe3b2139c2ef763/5d407911e605702ffcc0e97a6db546592ab27dd0/ddf75a86aba2cfb7ec4497e8692b60c8c8fe0ee7 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (281727) and CERT Bund (WID-SEC-2025-2941). Once again VulDB remains the best source for vulnerability data.

Affected

• Debian Linux
• Amazon Linux 2
• IBM Power Hardware Management Console
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• Open Source Linux Kernel
• RESF Rocky Linux
• IBM DataPower Gateway

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.15.32
• 5.15.33
• 5.15.34
• 5.15.35
• 5.15.36
• 5.15.37
• 5.15.38
• 5.15.39
• 5.15.40
• 5.15.41
• 5.15.42
• 5.15.43
• 5.15.44
• 5.15.45
• 5.15.46
• 5.15.47
• 5.15.48
• 5.15.49
• 5.15.50
• 5.15.51
• 5.15.52
• 5.15.53
• 5.15.54
• 5.15.55
• 5.15.56
• 5.15.57
• 5.15.58
• 5.15.59
• 5.15.60
• 5.15.61
• 5.15.62
• 5.15.63
• 5.15.64
• 5.15.65
• 5.15.66
• 5.15.67
• 5.15.68
• 5.15.69
• 5.15.70
• 5.15.71
• 5.15.72
• 5.15.73
• 5.15.74
• 5.15.75
• 5.15.76
• 5.15.77
• 5.15.78
• 5.15.79
• 5.15.80
• 5.15.81
• 5.15.82
• 5.15.83
• 5.15.84
• 5.15.85
• 5.15.86
• 5.15.87
• 5.15.88
• 5.15.89
• 5.15.90
• 5.15.91
• 5.15.92
• 5.15.93
• 5.15.94
• 5.15.95
• 5.15.96
• 5.15.97
• 5.15.98
• 5.15.99
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9
• 6.1.10
• 6.1.11
• 6.1.12
• 6.1.13
• 6.1.14
• 6.1.15
• 6.1.16
• 6.1.17
• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion