Linux Kernel up to 7.3.2 xen-netback xenvif_mcast_addr_list_free race condition

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 3.15- |
Summary
A vulnerability was found in Linux Kernel up to 7.3.2 and classified as very critical. This vulnerability affects the function xenvif_mcast_addr_list_free of the component xen-netback. The manipulation results in race condition.
This vulnerability is reported as CVE-2026-100081. The attack can be launched remotely. No exploit exists.
It is suggested to upgrade the affected component.
Details
A vulnerability classified as very critical has been found in Linux Kernel up to 7.3.2. Affected is the function xenvif_mcast_addr_list_free of the component xen-netback. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: xen-netback: defer xenvif_mcast_addr_list_free() In order for the function to legitimately avoid locking/RCU, it needs to run after all TX/RX processing has finished/stopped: Lookups happen from xenvif_start_xmit(), while adds/removes happen from xenvif_tx_action() (called out of xenvif_poll()). Move the call out of xenvif_disconnect_data() (the call to the function from connect()'s error path doesn't require any cleaning up there), and put it past the synchronization point in backend_disconnect(). This is XSA-527 / CVE-2026-100081.
The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-100081 since 09/25/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 11/06/2026).
Upgrading to version 5.10.274, 5.15.225, 6.1.192, 6.6.162, 6.12.116, 6.18.62 or 7.3.3 eliminates this vulnerability. Applying the patch 96e05a8ce243e2207704e2e7a6e7d1172730f515/0e786123e46d08d2247ce93a5435e45ed9f4c5d1/990d123d9eaa3ac6c979eed245658676d65ce0db/0d515c409033c8e2a645a781be3ca76ab825fc8c/a6bb2f1fa62c56279bdcdadce28d1310c5e12b62/34f0f63dc6dc11895a17bb5672451b6b11622c99/fb38fc58acb26d74fe8f7b19621fafaae3c040ff is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 5.10.273
- 5.15.224
- 6.1.191
- 6.6.161
- 6.12.115
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 6.18.52
- 6.18.53
- 6.18.54
- 6.18.55
- 6.18.56
- 6.18.57
- 6.18.58
- 6.18.59
- 6.18.60
- 6.18.61
- 7.3.0
- 7.3.1
- 7.3.2
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.274/5.15.225/6.1.192/6.6.162/6.12.116/6.18.62/7.3.3
Patch: 96e05a8ce243e2207704e2e7a6e7d1172730f515/0e786123e46d08d2247ce93a5435e45ed9f4c5d1/990d123d9eaa3ac6c979eed245658676d65ce0db/0d515c409033c8e2a645a781be3ca76ab825fc8c/a6bb2f1fa62c56279bdcdadce28d1310c5e12b62/34f0f63dc6dc11895a17bb5672451b6b11622c99/fb38fc58acb26d74fe8f7b19621fafaae3c040ff
Timeline
09/25/2026 CVE reserved11/06/2026 Advisory disclosed
11/06/2026 VulDB entry created
11/06/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CNA: Linux
CVE: CVE-2026-100081 (🔒)
GCVE (CVE): GCVE-0-2026-100081
GCVE (VulDB): GCVE-100-432072
Entry
Created: 11/06/2026 19:43Changes: 11/06/2026 19:43 (59)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.