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

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

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

canceldelayedworksync() is called before i2cmuxdeladapters() in rtl2832remove(). While the cancel waits for any running instance of i2cgatework to finish, it does not prevent the timer from being rescheduled by a concurrent thread.

During probe, the r820tattach() call attempts I2C transfers through the mux adapter. These transfers go through i2cmuxmasterxfer(), which calls rtl2832deselect() after the transfer completes, rescheduling i2cgatework via scheduledelayedwork(). If this transfer is still in flight when rtl2832remove() runs, rtl2832deselect() can reschedule i2cgatework after it has been cancelled, causing a use-after-free when kfree(dev) is called.

Fix this by calling i2cmuxdeladapters() before canceldelayedworksync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832deselect() can no longer reschedule i2cgatework. The subsequent canceldelayedworksync() is then guaranteed to be final.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Fix the driver by calling i2c_mux_del_adapters() before the r820t_attach() call attempts I2C transfers through the mux adapter (to prevent I2C transfers going through i2c_mux_master_xfer() after mux adapter unregistration).

    Linux kernel media driver rtl2832 i2c_mux_del_adapters() call order = Call i2c_mux_del_adapters() before r820t_attach() attempts I2C transfers
  2. Configuration

    In rtl2832_remove(), ensure cancel_delayed_work_sync() is called before i2c_mux_del_adapters() so the delayed work is not rescheduled concurrently and to prevent use-after-free when kfree(dev) is called.

    Linux kernel rtl2832 driver cancel_delayed_work_sync() placement = Call cancel_delayed_work_sync() before i2c_mux_del_adapters()

Event History

Aug 10, 2026
CVE Published
via MITRE·12:00 PM
Data Sourced
via MITRE·12:00 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68214?

CVE-2026-68214 has a risk score of 44, indicating a significant security vulnerability in the Linux kernel.

2

What does CVE-2026-68214 involve?

CVE-2026-68214 involves a use-after-free vulnerability in the rtl2832_remove() function of the Linux kernel.

3

How do I fix CVE-2026-68214?

To fix CVE-2026-68214, update your Linux kernel to the latest version where the vulnerability has been addressed.

4

What systems are affected by CVE-2026-68214?

CVE-2026-68214 affects systems running specific versions of the Linux kernel that utilize the rtl2832 media drivers.

5

What is the primary function impacted by CVE-2026-68214?

CVE-2026-68214 primarily impacts the rtl2832_remove() function, which is responsible for handling the rtl2832 media device removal.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203