CVE-2022-49305 drivers: staging: rtl8192u: Fix deadlock in ieee80211_beacons_stop()

Medium 5.5 Published Updated

A race condition in the rtl8192u driver causes a deadlock, leading to a denial of service in the Linux kernel.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2022-49305?

CVE-2022-49305 is a medium-severity vulnerability in Linux kernel, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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

drivers: staging: rtl8192u: Fix deadlock in ieee80211_beacons_stop()

There is a deadlock in ieee80211_beacons_stop(), which is shown below:

(Thread 1) | (Thread 2) | ieee80211_send_beacon() ieee80211_beacons_stop() | mod_timer() spin_lock_irqsave() //(1) | (wait a time) ... | ieee80211_send_beacon_cb() del_timer_sync() | spin_lock_irqsave() //(2) (wait timer to stop) | ...

We hold ieee->beacon_lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need ieee->beacon_lock in position (2) of thread 2. As a result, ieee80211_beacons_stop() will block forever.

This patch extracts del_timer_sync() from the protection of spin_lock_irqsave(), which could let timer handler to obtain the needed lock.

Weakness: CWE-667

Which versions are affected by CVE-2022-49305?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2022-49305?

Apply the vendor's patch.

Is CVE-2022-49305 being exploited?

There is no known exploitation of CVE-2022-49305 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as DEBIAN-CVE-2022-49305, GHSA-283v-8hg2-53qv, UBUNTU-CVE-2022-49305.

Is CVE-2022-49305 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free