Linux Kernel up to 6.19.5 __tegra_channel_try_format memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.1.166/6.6.129/6.12.76/6.18.16/6.19.5. This affects the function __tegra_channel_try_format. The manipulation leads to memory leak. This vulnerability is documented as CVE-2026-43162. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.1.166/6.6.129/6.12.76/6.18.16/6.19.5. This issue affects the function __tegra_channel_try_format. 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. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: media: tegra-video: Fix memory leak in __tegra_channel_try_format() The state object allocated by __v4l2_subdev_state_alloc() must be freed with __v4l2_subdev_state_free() when it is no longer needed. In __tegra_channel_try_format(), two error paths return directly after v4l2_subdev_call() fails, without freeing the allocated 'sd_state' object. This violates the requirement and causes a memory leak. Fix this by introducing a cleanup label and using goto statements in the error paths to ensure that __v4l2_subdev_state_free() is always called before the function returns.

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-43162 since 05/01/2026. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 6.1.167, 6.6.130, 6.12.77, 6.18.17 or 6.19.6 eliminates this vulnerability. Applying the patch 6c6f419fa9c44a4b7149b0292e01bff47308ba14/ca921be7a1174d5d58b28f84b683c2c0079f18c5/3ca2f09061736e72ef25eec2597d00f7f44094d3/2dff8966a3a889dd9d248a7e15d963b4097efcc5/d92e9a18f97a1d19d4c2ff81dcfbe43591f75b5a/43e5302d22334f1183dec3e0d5d8007eefe2817c 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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.167/6.6.130/6.12.77/6.18.17/6.19.6
Patch: 6c6f419fa9c44a4b7149b0292e01bff47308ba14/ca921be7a1174d5d58b28f84b683c2c0079f18c5/3ca2f09061736e72ef25eec2597d00f7f44094d3/2dff8966a3a889dd9d248a7e15d963b4097efcc5/d92e9a18f97a1d19d4c2ff81dcfbe43591f75b5a/43e5302d22334f1183dec3e0d5d8007eefe2817c

Timelineinfo

05/01/2026 CVE reserved
05/06/2026 +5 days Advisory disclosed
05/06/2026 +0 days VulDB entry created
05/17/2026 +11 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43162 (🔒)
GCVE (CVE): GCVE-0-2026-43162
GCVE (VulDB): GCVE-100-361451

Entryinfo

Created: 05/06/2026 16:47
Updated: 05/17/2026 14:14
Changes: 05/06/2026 16:47 (58), 05/17/2026 14:14 (10)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!