CVE-2023-54266

media: dvb-usb: m920x: Fix a potential memory leak in m920x_i2c_xfer()

N/A
Published: December 30, 2025 at 12:15 PM UTC
Updated: June 17, 2026 at 06:47 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: m920x: Fix a potential memory leak in m920x_i2c_xfer() 'read' is freed when it is known to be NULL, but not when a read error occurs. Revert the logic to avoid a small leak, should a m920x_read() call fail.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.4.300v ≥ 4.9.298v ≥ 5.16.34.14.263 ≤ v < 4.14.3264.19.226 ≤ v < 4.19.2954.4.300 ≤ v < 4.54.9.298 ≤ v < 4.105.10.94 ≤ v < 5.10.1955.15.17 ≤ v < 5.15.1325.16.3 ≤ v < 5.175.17 ≤ v < 6.1.535.17 ≤ v < 6.4.165.17 ≤ v < 6.5.35.17 ≤ v < 6.65.4.174 ≤ v < 5.4.2570c044e39d52abfbb4cb43dbc5a09c1dc1ed24648273cac7a89712ba6b898214af150b71dc33abe0c4.14.2634.19.2264.4.3004.9.2985.10.945.15.175.16.35.175.4.1747dca4428d7eb33c89979e620228fe557593fde6682ce3084892c0c0e006ec61f6144f2cc4e5ece88830e5d1b4344c2575020ee4bdf63fb48e2b56ce38cb4f0da9926277101d18d817048e1328ac2563a2ab06d7c4d6bfd0b545a768247a70463e977e27b7e221dc8f23727e00a7fb6709b3318547a7c4d8fe791612afabaeee9b911bd7b955985bcf5ff314
Vendor states this is fixed in 2b6e20ef0585a467c24c7e4fde28518e5b33225a (fixed)
Vendor states this is fixed in 2cc9f11aeae2887a4db25c27323fc445f4b49e86 (fixed)
Vendor states this is fixed in 4feed3dfca722c6d74865a37cab853c58e6aa190 (fixed)
Vendor states this is fixed in 75d6ef197c488cd852493b4a419274e3489da79d (fixed)
Vendor states this is fixed in 7ca7cd02114ac8caa6b0a64734b9af6be1559353 (fixed)
Vendor states this is fixed in 809623fedc31f4e74039d93bb75a8993635d7534 (fixed)
Vendor states this is fixed in c0178e938f110cdf6937f26975c0c951dbb1d9db (fixed)
Vendor states this is fixed in d13a84874a2e0236c9325b3adc8e126d0888ad6b (fixed)
Vendor states this is fixed in ea9ef6c2e001c5dc94bee35ebd1c8a98621cf7b8 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.14.326 (unaffected)
Vendor states this is fixed in 4.19.295 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.195 (unaffected)
Vendor states this is fixed in 5.15.132 (unaffected)
Vendor states this is fixed in 5.17 (unaffected)
Vendor states this is fixed in 5.4.257 (unaffected)
Vendor states this is fixed in 6.1.53 (unaffected)
Vendor states this is fixed in 6.4.16 (unaffected)
Vendor states this is fixed in 6.5.3 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card