CVE-2021-47396: mac80211-hwsim: fix late beacon hrtimer handling
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.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel issue in the mac80211-hwsim Wi-Fi simulation driver. When a high-resolution timer fires late, the driver can repeatedly try to catch up on missed beacon deadlines, causing stalls. The bundle does not show real-world exploitation, CVSS, or impact beyond availability-style disruption.
Executive priority
Treat this as a low-priority kernel maintenance item unless your organization relies on mac80211-hwsim for testing at scale. It does not currently justify emergency response based on the supplied evidence, but fixed kernels should be adopted through normal patch cycles.
Technical view
The vulnerable logic rearmed an hrtimer to deadlines that could already be in the past after delayed execution, especially under vCPU scheduling. The resolved change uses hrtimer_forward_now() so the next beacon timer resumes at the next interval after current time instead of replaying missed intervals.
Likely exposure
Exposure appears limited to Linux systems using or testing mac80211-hwsim, a simulated Wi-Fi environment. General production Linux hosts are less likely to be exposed unless this driver is present, enabled, and exercised. Exact downstream distribution status requires vendor kernel advisory checks.
Exploitation context
The sources cite syzbot-style reporting and vCPU scheduling delays, not public exploitation. KEV is false in the bundle, and no cited source states active exploitation. The practical concern is local or test-environment availability impact from timer-induced stalls.
Researcher notes
The record lacks CVSS, CWE, and detailed exploitability analysis. The root cause is timer catch-up behavior after late hrtimer firing in a simulation driver. Analysis should focus on availability, reachable configurations, and whether downstream kernels include the stable commits.
Mitigation direction
Update to a vendor kernel containing the referenced Linux stable fixes.
Check distribution advisories for backported fixes before relying on version numbers alone.
Prioritize systems that load or exercise mac80211-hwsim in CI, labs, or virtualized testing.
Remove or disable unused mac80211-hwsim functionality only according to vendor guidance.
Validation and detection
Inventory kernels and confirm whether the stable fix commits are present or backported.
Check whether mac80211-hwsim is built, loadable, loaded, or used in test workflows.
Review affected virtualized test systems for kernel stalls during simulated Wi-Fi beacon handling.
Confirm remediation through vendor package metadata or kernel changelog evidence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47396 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.