Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion
A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex. Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-94023
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 14:23 UTC · Revision 1
Source evidence
Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion
core-osv · Original sourcePublished 20 Oct 2026, 15:18 UTC
A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex. Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.
osv:CVE-2026-94023
Complete source record
{
"id": "1b94061b34516cbf0c40121a7191bc4f05e9623b8a8f851ef103cb6992132c9a",
"url": "https://osv.dev/vulnerability/CVE-2026-94023",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion",
"summary": "A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex. Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.",
"evidence": "osv:CVE-2026-94023",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-94023",
"aliases": [
"CVE-2026-94023",
"GHSA-36vf-7cx6-9f9j"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/eclipse-threadx/threadx",
"type": "GIT",
"events": [
{
"introduced": "6a018a4cfda937c0d8cbdee761187c5c5843e115"
},
{
"last_affected": "b91b03b9e75fa523b17127f9e0eca09dca916459"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "6.0.1"
},
{
"last_affected": "6.5.1.202602a"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
}
],
"versions": [
"v6.4.1_rel",
"v6.5.1.202602a_rel",
"v6.5.1.202602_rel",
"v6.5.0.202601_rel",
"v6.4.5.202504_rel",
"v6.4.3.202503_rel",
"v6.4.2_rel",
"v6.4.0_rel",
"v6.3.0_rel",
"v6.2.1_rel",
"v6.2.0_rel",
"v6.1.12_rel",
"v6.1.11_rel",
"v6.1.10_rel",
"v6.1.9_rel",
"v6.1.8_rel",
"v6.1.7_rel",
"v6.1.6_rel",
"v6.1.5_rel",
"v6.1.3_rel",
"v6.1.2_rel",
"v6.1.1_rel",
"v6.1_rel",
"v6.0.2_rel",
"v6.0.1_rel"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-94023.json"
}
}
],
"modified": "2026-10-28T02:30:29.250205087Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/94xxx/CVE-2026-94023.json",
"https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-36vf-7cx6-9f9j",
"https://nvd.nist.gov/vuln/detail/CVE-2026-94023"
],
"provider_metadata": {
"cwe_ids": [
"CWE-125",
"CWE-862"
],
"cna_assigner": "eclipse",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/94xxx/CVE-2026-94023.json"
}
},
"related_cves": [
{
"value": "CVE-2026-94023",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 496316,
"published_at": "2026-10-20T15:18:09.957+00:00"
}