CVE-2026-68214

media: rtl2832: fix use-after-free in rtl2832_remove()

N/A
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM 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: rtl2832: fix use-after-free in rtl2832_remove() cancel_delayed_work_sync() is called before i2c_mux_del_adapters() in rtl2832_remove(). While the cancel waits for any running instance of i2c_gate_work to finish, it does not prevent the timer from being rescheduled by a concurrent thread. During probe, the r820t_attach() call attempts I2C transfers through the mux adapter. These transfers go through i2c_mux_master_xfer(), which calls rtl2832_deselect() after the transfer completes, rescheduling i2c_gate_work via schedule_delayed_work(). If this transfer is still in flight when rtl2832_remove() runs, rtl2832_deselect() can reschedule i2c_gate_work after it has been cancelled, causing a use-after-free when kfree(dev) is called. Fix this by calling i2c_mux_del_adapters() before cancel_delayed_work_sync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832_deselect() can no longer reschedule i2c_gate_work. The subsequent cancel_delayed_work_sync() is then guaranteed to be final.

Affected

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

4.7 ≤ v < 5.10.2654.7 ≤ v < 5.15.2164.7 ≤ v < 6.1.1834.7 ≤ v < 6.12.1014.7 ≤ v < 6.18.424.7 ≤ v < 6.6.1484.7 ≤ v < 7.1.64.7 ≤ v < 7.24.7cddcc40b1b1553010acb89add84c64b5d123ec94
Vendor states this is fixed in 13c06056699e66ff7109ba68658cc6ea4a23f516 (fixed)
Vendor states this is fixed in 1e8a6bc19403661661fed5ae82f6eca6c9cdfad2 (fixed)
Vendor states this is fixed in 24bef237eef8dd1ebcffb129ba21891ddad0d309 (fixed)
Vendor states this is fixed in 2c71bda6edc630a1f8c3c45d8df5fc22d234e042 (fixed)
Vendor states this is fixed in 680daf40a82d483949f87f0d8f98639dc47e610c (fixed)
Vendor states this is fixed in 68a9c0290897c1436ddceb8cea604c93377a0299 (fixed)
Vendor states this is fixed in 90d781711418881f8c836c2a859cc2886625d750 (fixed)
Vendor states this is fixed in 9acd5bbbe1df8e487e49488692c224496d4c9e16 (fixed)
Vendor states this is fixed in 4.7 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (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

StatusRECEIVED

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