CVE-2026-99512 in Linuxinfo

Summary

by MITRE • 11/19/2026

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

media: au0828: fix use-after-free in bulk_timeout timer on disconnect

start_urb_transfer() arms dev->bulk_timeout, whose callback au0828_bulk_timeout() queues dev->restart_streaming; that work in turn calls start_urb_transfer() and re-arms the timer.

au0828_dvb_unregister() cancels restart_streaming on disconnect but does not sync bulk_timeout. au0828_usb_release() then frees dev with kfree(), so a timer still armed or pending at that point can fire after the free and dereference dev through timer_container_of().

Sync the timer with timer_shutdown_sync() before cancel_work_sync(). The timer callback queues the work, so the timer must be stopped first; the shutdown variant is needed because the work re-arms the timer through start_urb_transfer(). The dvb->frontend == NULL early return guards the register-failure path where the timer was never set up.

This bug was found by static analysis.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The vulnerability identified in the Linux kernel media driver for au0828 devices represents a critical use-after-free condition triggered during device disconnection sequences. This flaw arises from an improper synchronization of hardware timers and workqueue structures within the USB subsystem handling logic. Specifically, the function start_urb_transfer() arms a timer designated as dev->bulk_timeout, which is configured to invoke the callback au0828_bulk_timeout(). This callback subsequently queues a restart_streaming work item that calls back into start_urb_transfer(), thereby re-arming the same timer and creating a recursive dependency loop between the timer expiration mechanism and the kernel workqueue execution path.

The core technical flaw lies in the cleanup sequence executed during device removal operations. When au0828_dvb_unregister() is invoked to handle disconnect events, it correctly cancels the restart_streaming work item using cancel_work_sync(). However, it fails to synchronize or stop the underlying bulk_timeout timer before proceeding with memory deallocation. Consequently, if the timer was armed or pending at the moment of disconnection, its expiration handler may execute after the device structure has been freed by kfree() in au0828_usb_release(). Since the timer callback relies on timer_container_of to retrieve a pointer to the dev structure, this race condition results in dereferencing memory that is no longer valid.

This use-after-free vulnerability poses significant operational risks including kernel panic, data corruption, and potential privilege escalation if an attacker can influence the timing of device disconnection or manipulate memory allocation patterns post-failure. The exploitation vector typically involves triggering a disconnect event while bulk transfer operations are active, forcing the timer to fire after the driver has released its internal state structures. Such scenarios compromise system stability and integrity by allowing execution in arbitrary kernel memory spaces that may contain attacker-controlled data following reallocation of the freed region.

The remediation strategy implemented addresses this race condition by introducing proper synchronization primitives before resource release. The fix employs timer_shutdown_sync() to ensure both pending and currently executing instances of the bulk_timeout handler are completed and prevented from re-arming themselves prior to freeing device resources. This approach is necessary because simply calling del_timer_sync would not suffice due to the recursive nature where the work item restarts the timer; thus, shutdown synchronization guarantees complete cessation before memory deallocation occurs. Additionally, an early return guard checking for dvb->frontend == NULL ensures that cleanup routines do not attempt operations on uninitialized timers in failure paths during device registration.

From a classification perspective, this vulnerability aligns with CWE-416 Use After Free and falls under the ATT&CK technique of Taint Analysis or potentially exploitation via memory corruption depending on specific context. It highlights common pitfalls in kernel driver development regarding lifecycle management of asynchronous hardware resources like USB bulk transfer timers. Developers must ensure strict ordering when tearing down complex subsystem interactions involving periodic callbacks that may recursively re-arm themselves, as standard cancellation functions often do not account for such self-restarting behaviors without explicit shutdown synchronization mechanisms provided by the timer API.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00208

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!