CVE-2026-100080Linux vulnerability
CVE-2026-100080 is a vulnerability in Linux, not yet scored.
Why this priority: Not scored yet, and no exploitation signal.
Published · Updated · NVD status: Received
What it is
The record does not classify the weakness yet; the description below says what the reporter found.
How it is reached
The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.
What an attacker gains
Its impact has not been scored yet.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade Linux to a fixed version for your release line (5.10.274, 5.15.225, 6.1.192).
Description from NVD
In the Linux kernel, the following vulnerability has been resolved:
xen-netback: Fix UAF when reading statistics data
The network statistic data in the driver is protected by RCU. Unfortunately when tearing down the queues after an error during connecting to the frontend (e.g. due to illegal Xenstore data filled in by the guest), the statistic data is being freed without synchronizing the RCU state. In case the data is being read via sysfs in this phase, access to already freed memory or memory being in new use is possible.
Fix that by calling synchronize_net() before freeing the queue data.
This is XSA-526 / CVE-2026-100080
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Linux. Start from where it runs and what it is connected to.
Trust boundaries in play
Questions to answer about your own systems
- Where does Linux run in your systems, and at which version?
- Which of those instances are reachable by people you do not trust?
- What can it reach once compromised: which data stores, secrets and services?
Read more
More reading
- git.kernel.org/stable/c/36f858f228e3f955b9336af7f94634747c221518
- git.kernel.org/stable/c/37d5a73170579b30e67cc8b19ec69715eea3a6b6
- git.kernel.org/stable/c/4223b33be49ee09acb6f1d26beb4a36dd3b8d63a
- git.kernel.org/stable/c/4867687b6ad28ab84bc0811d8f8f9972e769da02
- git.kernel.org/stable/c/6cd611d2abdd8623a554e14145f82c1cb4e4467a
- git.kernel.org/stable/c/89e534265b62c94749639350200b10370564bb3a
- git.kernel.org/stable/c/ab9cdf1291be551da999510b30216a2886074d7a
- www.openwall.com/lists/oss-security/2026/11/06/9
- xenbits.xen.org/xsa/advisory-526.html
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.