GHSA-P7QH-G4F5-GXQ9
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
ocfs2/cluster: keep heartbeat local node stable
o2nm_node_local_store() handles local=0 by stopping o2net and setting cl_local_node to O2NM_INVALID_NODE_NUM, but it leaves cl_has_local set. That stale state makes o2nm_this_node() return 255, blocks a later local=1 attempt with -EBUSY, and can feed 255 to heartbeat users that call o2nm_this_node() dynamically.
Clearing cl_has_local is required when the local node is reset. But heartbeat threads can still be running at that point. They pin the local node config item at startup, yet o2hb_do_disk_heartbeat() and thread teardown re-read o2nm_this_node() for the local slot and for o2nm_undepend_this_node(). Once local=0 has cleared the live local-node state, those dynamic reads return O2NM_MAX_NODES, which is also the invalid node number 255.
Store the local node number in the heartbeat region when the region starts. Use that stable node for heartbeat slot writes/checks, negotiation messages, and the final configfs undepend. Stop the heartbeat loop when the current local node no longer matches the stored node, and clear cl_has_local together with cl_local_node in the local=0 path so nodemanager state matches node removal.
Validation reproduced this kernel report: KASAN slab-out-of-bounds in o2hb_do_disk_heartbeat+0x372/0xb30 RIP: 0010:memset+0xf/0x20 Read of size 8 Call trace: dump_stack_lvl+0x66/0xa0 print_report+0xd0/0x630 o2hb_do_disk_heartbeat+0x372/0xb30 (fs/ocfs2/cluster/heartbeat.c:1079) srso_alias_return_thunk+0x5/0xfbef5 __virt_addr_valid+0x188/0x2f0 kasan_report+0xe4/0x120 o2hb_do_disk_heartbeat+0x5/0xb30 (fs/ocfs2/cluster/heartbeat.c:1079) o2hb_thread+0x14e/0x770 kthread_affine_node+0x139/0x180 lockdep_hardirqs_on_prepare+0xda/0x190 trace_hardirqs_on+0x18/0x130 kthread+0x19d/0x1e0 ret_from_fork+0x37a/0x4d0 __switch_to+0x2d5/0x6f0 ret_from_fork_asm+0x1a/0x30
{
"affected": [],
"aliases": [
"CVE-2026-90322"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:30Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2/cluster: keep heartbeat local node stable\n\no2nm_node_local_store() handles local=0 by stopping o2net and setting\ncl_local_node to O2NM_INVALID_NODE_NUM, but it leaves cl_has_local set. \nThat stale state makes o2nm_this_node() return 255, blocks a later local=1\nattempt with -EBUSY, and can feed 255 to heartbeat users that call\no2nm_this_node() dynamically.\n\nClearing cl_has_local is required when the local node is reset. But\nheartbeat threads can still be running at that point. They pin the local\nnode config item at startup, yet o2hb_do_disk_heartbeat() and thread\nteardown re-read o2nm_this_node() for the local slot and for\no2nm_undepend_this_node(). Once local=0 has cleared the live local-node\nstate, those dynamic reads return O2NM_MAX_NODES, which is also the\ninvalid node number 255.\n\nStore the local node number in the heartbeat region when the region\nstarts. Use that stable node for heartbeat slot writes/checks,\nnegotiation messages, and the final configfs undepend. Stop the heartbeat\nloop when the current local node no longer matches the stored node, and\nclear cl_has_local together with cl_local_node in the local=0 path so\nnodemanager state matches node removal.\n\nValidation reproduced this kernel report:\nKASAN slab-out-of-bounds in o2hb_do_disk_heartbeat+0x372/0xb30\nRIP: 0010:memset+0xf/0x20\nRead of size 8\nCall trace:\n dump_stack_lvl+0x66/0xa0\n print_report+0xd0/0x630\n o2hb_do_disk_heartbeat+0x372/0xb30 (fs/ocfs2/cluster/heartbeat.c:1079)\n srso_alias_return_thunk+0x5/0xfbef5\n __virt_addr_valid+0x188/0x2f0\n kasan_report+0xe4/0x120\n o2hb_do_disk_heartbeat+0x5/0xb30 (fs/ocfs2/cluster/heartbeat.c:1079)\n o2hb_thread+0x14e/0x770\n kthread_affine_node+0x139/0x180\n lockdep_hardirqs_on_prepare+0xda/0x190\n trace_hardirqs_on+0x18/0x130\n kthread+0x19d/0x1e0\n ret_from_fork+0x37a/0x4d0\n __switch_to+0x2d5/0x6f0\n ret_from_fork_asm+0x1a/0x30",
"id": "GHSA-p7qh-g4f5-gxq9",
"modified": "2026-09-17T18:32:01Z",
"published": "2026-09-17T18:32:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90322"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/688bc88e2046dd6ce81ce18079b5254cb8dadc0e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/70d7bb7a0be033e5ebe8a2c48974692b1318891c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8abb2b7c60d2b2c0f40606048c873096c03874d2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8e5cb90f212fda9f6cd29915a1ed74353108ceb3"
}
],
"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.