CVE-2026-68214
Last modified
CVE-2026-68214 is a vulnerability of currently unknown severity. 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.
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= cddcc40b1b1553010acb89add84c64b5d123ec94, < 9acd5bbbe1df8e487e49488692c224496d4c9e16; >= cddcc40b1b1553010acb89add84c64b5d123ec94, < 24bef237eef8dd1ebcffb129ba21891ddad0d309; >= cddcc40b1b1553010acb89add84c64b5d123ec94, < 2c71bda6edc630a1f8c3c45d8df5fc22d234e042; >= cddcc40b1b1553010acb89add84c64b5d123ec94, < 90d781711418881f8c836c2a859cc2886625d750; >= cddcc40b1b1553010acb89add84c64b5d123ec94, < 680daf40a82d483949f87f0d8f98639dc47e610c |
| Linux | Linux | 4.7 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68214?
How severe is CVE-2026-68214?
How do I fix CVE-2026-68214?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68209In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6821GitLab has remediated an issue in GitLab EE affecting all ve…4.3
- CVE-2026-68210In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68211In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68212In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68213In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68215In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68216In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68217In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68218In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68219In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68220In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68214?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
