media: tegra-video: Fix memory leak in __tegra_channel_try_format()
Summary
| CVE | CVE-2026-43162 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-06 12:16:34 UTC |
| Updated | 2026-05-13 21:19:56 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-401
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 1ebaeb09830f36c1111b72a95420814225bd761c 6c6f419fa9c44a4b7149b0292e01bff47308ba14 git | Not specified |
| CNA | Linux | Linux | affected 1ebaeb09830f36c1111b72a95420814225bd761c ca921be7a1174d5d58b28f84b683c2c0079f18c5 git | Not specified |
| CNA | Linux | Linux | affected 1ebaeb09830f36c1111b72a95420814225bd761c 3ca2f09061736e72ef25eec2597d00f7f44094d3 git | Not specified |
| CNA | Linux | Linux | affected 1ebaeb09830f36c1111b72a95420814225bd761c 2dff8966a3a889dd9d248a7e15d963b4097efcc5 git | Not specified |
| CNA | Linux | Linux | affected 1ebaeb09830f36c1111b72a95420814225bd761c d92e9a18f97a1d19d4c2ff81dcfbe43591f75b5a git | Not specified |
| CNA | Linux | Linux | affected 1ebaeb09830f36c1111b72a95420814225bd761c 43e5302d22334f1183dec3e0d5d8007eefe2817c git | Not specified |
| CNA | Linux | Linux | affected 5.10 | Not specified |
| CNA | Linux | Linux | unaffected 5.10 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.130 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.77 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.17 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.6 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/ca921be7a1174d5d58b28f84b683c2c0079f18c5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/3ca2f09061736e72ef25eec2597d00f7f44094d3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/d92e9a18f97a1d19d4c2ff81dcfbe43591f75b5a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/2dff8966a3a889dd9d248a7e15d963b4097efcc5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/6c6f419fa9c44a4b7149b0292e01bff47308ba14 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/43e5302d22334f1183dec3e0d5d8007eefe2817c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.