GHSA-PG3G-FX7X-75V9
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
xen/xenbus: check otherend_id only after it has been initialized
When device just got initialized (for example on module load), the otherend_id field is initialized only after xenbus_read_otherend_details() gets called. If xenstore watch triggers xenbus_dev_changed() before that, it might consider still zeroed otherend_id field (not matching actual xenstore content) as a sign of device state reset. It can happen because xenstore watch are handled in another thread (xenwatch), which can run in parallel to the initial device probe running at module load. In that case, it would call device_unregister(), which would deadlock against device probe from module init.
Fix this by considering dev->otherend_id change only after dev->otherend is set (which happen after otherend_id is initialized).
{
"affected": [],
"aliases": [
"CVE-2026-90310"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:28Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxen/xenbus: check otherend_id only after it has been initialized\n\nWhen device just got initialized (for example on module load), the\notherend_id field is initialized only after\nxenbus_read_otherend_details() gets called. If xenstore watch triggers\nxenbus_dev_changed() before that, it might consider still zeroed\notherend_id field (not matching actual xenstore content) as a sign of\ndevice state reset. It can happen because xenstore watch are handled in\nanother thread (xenwatch), which can run in parallel to the initial\ndevice probe running at module load. In that case, it would call\ndevice_unregister(), which would deadlock against device probe from\nmodule init.\n\nFix this by considering dev-\u003eotherend_id change only after dev-\u003eotherend\nis set (which happen after otherend_id is initialized).",
"id": "GHSA-pg3g-fx7x-75v9",
"modified": "2026-09-17T18:32:00Z",
"published": "2026-09-17T18:32:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90310"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/36fb592af353c55832e2cafe3fcfc3291be05f19"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c76cbf348c7df077f93fa99a1225a527ce64cfa1"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.