🛡️ AZL-35474 — hyperv-daemons
Description
CVE-2024-26583 affecting package hyperv-daemons for versions less than 6.6.22.1-2
In the Linux kernel, the following vulnerability has been resolved:
tls: fix race between async notify and socket close
The submitting thread (one which called recvmsg/sendmsg)
may exit as soon as the async crypto handler calls complete()
so any code past that point risks touching already freed data.
Try to avoid the locking and extra flags altogether.
Have the main thread hold an extra reference, this way
we can depend solely on the atomic ref counter for
synchronization.
Don't futz with reiniting the completion, either, we are now
tightly controlling when completion fires.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
Affected software
AZL-35474 is recorded against 1 package.
- hyperv-daemons (fixed in 6.6.22.1-2)
Timeline and source
Published on 21 February 2024 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| hyperv-daemons | — | 6.6.22.1-2 |
References
Similar Threats
More AZL 3 advisories
Browse all of AZL 3 in the advisory index.
Free Vulnerability Check
Is your site affected by AZL-35474?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-35474 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.