CVE-2021-47396

published 21 May 2024 · updated 11 May 2026

mac80211-hwsim: fix late beacon hrtimer handling

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2c204cf594df3b9468368dc9d0b24d482d93cda7, Kernel 313bbd1990b6ddfdaa7da098d0c56b098a833572, Kernel 9bee85de2c8155388c09a2e1530a243ec1c96f05 and 1 more.

In the Linux kernel, the following vulnerability has been resolved: mac80211-hwsim: fix late beacon hrtimer handling Thomas explained in https://lore.kernel.org/r/87mtoeb4hb.ffs@tglx that our handling of the hrtimer here is wrong: If the timer fires late (e.g. due to vCPU scheduling, as reported by Dmitry/syzbot) then it tries to actually rearm the timer at the next deadline, which might be in the past already: 1 2 3 N N+1 | | | ... | | ^ intended to fire here (1) ^ next deadline here (2) ^ actually fired here The next time it fires, it's later, but will still try to schedule for the next deadline (now 3), etc. until it catches up with N, but that might take a long time, causing stalls etc. Now, all of this is simulation, so we just have to fix it, but note that the behaviour is wrong even per spec, since there's no value then in sending all those beacons unaligned - they should be aligned to the TBTT (1, 2, 3, ... in the picture), and if we're a bit (or a lot) late, then just resume at that point. Therefore, change the code to use hrtimer_forward_now() which will ensure that the next firing of the timer would be at N+1 (in the picture), i.e. the next interval point after the current time.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.9, >=01e59e467ecf976c782eecd4dc99644802cc60e2 <2c204cf594df3b9468368dc9d0b24d482d93cda7, >=01e59e467ecf976c782eecd4dc99644802cc60e2 <313bbd1990b6ddfdaa7da098d0c56b098a833572, >=01e59e467ecf976c782eecd4dc99644802cc60e2 <9bee85de2c8155388c09a2e1530a243ec1c96f05, >=01e59e467ecf976c782eecd4dc99644802cc60e2 <ed2adf69e29848d1eb9df99633dde655421c92ed2c204cf594df3b9468368dc9d0b24d482d93cda7, 313bbd1990b6ddfdaa7da098d0c56b098a833572, 9bee85de2c8155388c09a2e1530a243ec1c96f05, ed2adf69e29848d1eb9df99633dde655421c92ed

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2021-47396 severity on Zeptric[![CVE-2021-47396](https://zeptric.io/badge/cve/CVE-2021-47396.svg)](https://zeptric.io/cve/CVE-2021-47396)