Linux Kernel up to 7.3.2 xen-blkback use after free

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 4.33- |
Summary
A vulnerability was found in Linux Kernel up to 7.3.2. It has been declared as very critical. Impacted is an unknown function of the component xen-blkback. Such manipulation leads to use after free. This vulnerability is traded as CVE-2026-100082. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 7.3.2. Affected by this issue is some unknown processing of the component xen-blkback. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: xen-blkback: Avoid UAF when reading I/O statistics Reading I/O statistics via sysfs concurrently with tearing down a frontend device might result in UAF or a NULL dereference, as the reading of the statistics data is not synchronized with freeing the data. Use a rwlock for synchronizing. This is XSA-528 / CVE-2026-100082
The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-100082 since 09/25/2026. The exploitation is known to be easy. The attack may be launched remotely. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (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 253cff0526781e28b1b0f9fdacd74ecdc23d3ab7/2c9ccbe0ffcff3615c7ad917c49b67571a41f21c/58ba056991dbcec8a75e6861cb4479ac947b69e6/fe9ead8c5bdb752e329cecfecbdb5dfca5e9996b/b764e17313534794aeb99c901869f213e36a16ef/c49934da934cf495faf782aa5d84f413221c9be6/b0378161c28e77e4d0e2eda3c9433ab4394d2a2f is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
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: Use after freeCWE: CWE-416 / CWE-119
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: 253cff0526781e28b1b0f9fdacd74ecdc23d3ab7/2c9ccbe0ffcff3615c7ad917c49b67571a41f21c/58ba056991dbcec8a75e6861cb4479ac947b69e6/fe9ead8c5bdb752e329cecfecbdb5dfca5e9996b/b764e17313534794aeb99c901869f213e36a16ef/c49934da934cf495faf782aa5d84f413221c9be6/b0378161c28e77e4d0e2eda3c9433ab4394d2a2f
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-100082 (🔒)
GCVE (CVE): GCVE-0-2026-100082
GCVE (VulDB): GCVE-100-432074
Entry
Created: 11/06/2026 19:44Changes: 11/06/2026 19:44 (58)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.