CVE-2021-47344

media: zr364xx: fix memory leak in zr364xx_start_readpipe

MEDIUM

5.5

CVSS Score

Published: May 21, 2024 at 02:35 PM UTC

Updated: June 17, 2026 at 04:17 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: media: zr364xx: fix memory leak in zr364xx_start_readpipe syzbot reported memory leak in zr364xx driver. The problem was in non-freed urb in case of usb_submit_urb() fail. backtrace: [<ffffffff82baedf6>] kmalloc include/linux/slab.h:561 [inline] [<ffffffff82baedf6>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74 [<ffffffff82f7cce8>] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022 [<ffffffff84251dfc>] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline] [<ffffffff84251dfc>] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516 [<ffffffff82bb6507>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396 [<ffffffff826018a9>] really_probe+0x159/0x500 drivers/base/dd.c:576

Affected

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

Linux Kernel · Linux

95%

2.6.32 ≤ v < 4.14.2402.6.32 ≤ v < 4.19.1982.6.32 ≤ v < 4.4.2762.6.32 ≤ v < 4.9.2762.6.32 ≤ v < 5.10.512.6.32 ≤ v < 5.12.182.6.32 ≤ v < 5.13.32.6.32 ≤ v < 5.142.6.32 ≤ v < 5.4.1334.10 ≤ v < 4.14.2404.15 ≤ v < 4.19.1984.20 ≤ v < 5.4.1334.5 ≤ v < 4.9.2765.11 ≤ v < 5.12.185.13 ≤ v < 5.13.35.5 ≤ v < 5.10.512.6.32ccbf035ae5de4c535160fc99f73feb44cc55b534

Vendor states this is fixed in 021c294dff030f3ba38eb81e400ba123db32ecbc (fixed)

Vendor states this is fixed in 0a045eac8d0427b64577a24d74bb8347c905ac65 (fixed)

Vendor states this is fixed in 0edd6759167295ea9969e89283b81017b4c688aa (fixed)

Vendor states this is fixed in 5f3f81f1c96b501d180021c23c25e9f48eaab235 (fixed)

Vendor states this is fixed in b0633051a6cb24186ff04ce1af99c7de18c1987e (fixed)

Vendor states this is fixed in bbc80a972a3c5d7eba3f6c9c07af8fea42f5c513 (fixed)

Vendor states this is fixed in c57b2bd3247925e253729dce283d6bf6abc9339d (fixed)

Vendor states this is fixed in c57bfd8000d7677bf435873b440eec0c47f73a08 (fixed)

Vendor states this is fixed in d69b39d89f362cfeeb54a68690768d0d257b2c8f (fixed)

Vendor states this is fixed in 2.6.32 (unaffected)

Vendor states this is fixed in 4.14.240 (unaffected)

Vendor states this is fixed in 4.19.198 (unaffected)

Vendor states this is fixed in 4.4.276 (unaffected)

Vendor states this is fixed in 4.9.276 (unaffected)

Vendor states this is fixed in 5.10.51 (unaffected)

Vendor states this is fixed in 5.12.18 (unaffected)

Vendor states this is fixed in 5.13.3 (unaffected)

Vendor states this is fixed in 5.14 (unaffected)

Vendor states this is fixed in 5.4.133 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references