CVE-2026-72143 (GCVE-0-2026-72143)
Vulnerability from cvelistv5 – Published: 2026-08-15 05:53 – Updated: 2026-10-16 18:44
VLAI
EPSS
VEX
Title
platform/x86: ISST: Restore SST-PP control to all domains
Summary
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: ISST: Restore SST-PP control to all domains
The SST-PP control offset is only restored to power domain 0 after
resume. During suspend, control values are read and stored for all
power domains.
Use pd_info->sst_base instead of power_domain_info->sst_base, which
only points to power domain 0 base address.
Severity
7.1 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-10-16 18:42 UTC
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
e3704ce5d7156ee837461be99841f312c64700b0 , < cea03d67db3a880893360bdbb1b0b8d9b33b1799
(git)
Affected: dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8 , < 2a42f651cce91e9cbe65fe933622c522cbb1868b (git) Affected: dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8 , < 2565a28cdcdcb035e151d285efcba26bccb3726e (git) Affected: 2624f3bf45a830cb3b8c8b967b23a72139700562 (git) Affected: 6.18.16 , < 6.18.40 (semver) Affected: 6.19.6 , < 6.20 (semver) |
|
| Linux | Linux |
Affected:
7.0
Unaffected: 0 , < 7.0 (semver) Unaffected: 6.18.40 , ≤ 6.18.* (semver) Unaffected: 7.1.5 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-72143",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T18:42:49.460532Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-16T18:44:58.966Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "cea03d67db3a880893360bdbb1b0b8d9b33b1799",
"status": "affected",
"version": "e3704ce5d7156ee837461be99841f312c64700b0",
"versionType": "git"
},
{
"lessThan": "2a42f651cce91e9cbe65fe933622c522cbb1868b",
"status": "affected",
"version": "dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8",
"versionType": "git"
},
{
"lessThan": "2565a28cdcdcb035e151d285efcba26bccb3726e",
"status": "affected",
"version": "dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8",
"versionType": "git"
},
{
"status": "affected",
"version": "2624f3bf45a830cb3b8c8b967b23a72139700562",
"versionType": "git"
},
{
"lessThan": "6.18.40",
"status": "affected",
"version": "6.18.16",
"versionType": "semver"
},
{
"lessThan": "6.20",
"status": "affected",
"version": "6.19.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.0"
},
{
"lessThan": "7.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.40",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.40",
"versionStartIncluding": "6.18.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "7.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "7.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.19.6",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: ISST: Restore SST-PP control to all domains\n\nThe SST-PP control offset is only restored to power domain 0 after\nresume. During suspend, control values are read and stored for all\npower domains.\n\nUse pd_info-\u003esst_base instead of power_domain_info-\u003esst_base, which\nonly points to power domain 0 base address."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.1,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The flawed writeq runs only in the ISST TPMI driver PM resume callback (intel_sst_resume -\u003e tpmi_sst_dev_resume) after a local suspend-to-RAM cycle, not from any network packet handler or remote service.\nAC:L - Once a multi-domain SST-TPMI system completes S3 suspend, resume deterministically executes the wrong MMIO restore for every power domain above zero with no races or attacker-dependent timing.\nPR:L - Reaching the buggy resume handler requires only initiating a system suspend (e.g., writing mem to /sys/power/state, which lacks a CAP_SYS_ADMIN check, or polkit-permitted local suspend); user namespaces cannot grant ISST ioctl writes but can still allow this PM path.\nUI:N - Exploitation does not require a victim to open files, mount filesystems, or take any other interactive action beyond the attacker (or system policy) triggering suspend and automatic resume.\nS:U - Impact is confined to corrupting SST-PP hardware configuration and host stability on the same machine; it does not cross a VM, container, or IOMMU security boundary to another authority.\nC:N - The bug performs MMIO writeq operations to hardware registers only; it does not read kernel memory, leak pointers, or expose data to userspace.\nI:H - Each incorrect resume writes a full 64-bit SST-PP control value to the wrong hardware MMIO address, corrupting platform power/performance configuration; values can be attacker-influenced via prior CAP_SYS_ADMIN ISST perf-level changes before suspend.\nA:H - Misdirected MMIO writes can panic or hang the host, and unrestored or corrupted SST-PP settings on additional power domains can destabilize multi-die Xeon systems after every affected resume cycle."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:40:51.234Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/cea03d67db3a880893360bdbb1b0b8d9b33b1799"
},
{
"url": "https://git.kernel.org/stable/c/2a42f651cce91e9cbe65fe933622c522cbb1868b"
},
{
"url": "https://git.kernel.org/stable/c/2565a28cdcdcb035e151d285efcba26bccb3726e"
}
],
"title": "platform/x86: ISST: Restore SST-PP control to all domains",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72143",
"datePublished": "2026-08-15T05:53:16.241Z",
"dateReserved": "2026-08-09T03:40:39.908Z",
"dateUpdated": "2026-10-16T18:44:58.966Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-72143",
"date": "2026-11-18",
"epss": "0.00169",
"percentile": "0.06329"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "cea03d67db3a880893360bdbb1b0b8d9b33b1799",
"status": "affected",
"version": "e3704ce5d7156ee837461be99841f312c64700b0",
"versionType": "git"
},
{
"lessThan": "2a42f651cce91e9cbe65fe933622c522cbb1868b",
"status": "affected",
"version": "dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8",
"versionType": "git"
},
{
"lessThan": "2565a28cdcdcb035e151d285efcba26bccb3726e",
"status": "affected",
"version": "dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8",
"versionType": "git"
},
{
"status": "affected",
"version": "2624f3bf45a830cb3b8c8b967b23a72139700562",
"versionType": "git"
},
{
"lessThan": "6.18.40",
"status": "affected",
"version": "6.18.16",
"versionType": "semver"
},
{
"lessThan": "6.20",
"status": "affected",
"version": "6.19.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.0"
},
{
"lessThan": "7.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.40",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: ISST: Restore SST-PP control to all domains\n\nThe SST-PP control offset is only restored to power domain 0 after\nresume. During suspend, control values are read and stored for all\npower domains.\n\nUse pd_info-\u003esst_base instead of power_domain_info-\u003esst_base, which\nonly points to power domain 0 base address."
}
],
"id": "CVE-2026-72143",
"lastModified": "2026-10-16T19:17:11.633",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.2,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-72143",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T18:42:49.460532Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-08-15T06:21:31.953",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2565a28cdcdcb035e151d285efcba26bccb3726e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2a42f651cce91e9cbe65fe933622c522cbb1868b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/cea03d67db3a880893360bdbb1b0b8d9b33b1799"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-07T10:56:47+00:00",
"cve": "CVE-2026-72143",
"id": "CVE-2026-72143",
"initial_release_date": "2026-08-15T00:00:00+00:00",
"product_status:known_affected": "108",
"product_status:known_not_affected": "92",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: platform/x86: ISST: Restore SST-PP control to all domains",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-72143.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-10-17T23:52:51Z",
"cve": "CVE-2026-72143",
"id": "CVE-2026-72143",
"initial_release_date": "2026-08-31T13:30:16Z",
"product_status:known_affected": "0",
"product_status:known_not_affected": "362",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-72143",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-72143.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-72143",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T18:42:49.460532Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-16T18:42:49.992Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "cea03d67db3a880893360bdbb1b0b8d9b33b1799",
"status": "affected",
"version": "e3704ce5d7156ee837461be99841f312c64700b0",
"versionType": "git"
},
{
"lessThan": "2a42f651cce91e9cbe65fe933622c522cbb1868b",
"status": "affected",
"version": "dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8",
"versionType": "git"
},
{
"lessThan": "2565a28cdcdcb035e151d285efcba26bccb3726e",
"status": "affected",
"version": "dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8",
"versionType": "git"
},
{
"status": "affected",
"version": "2624f3bf45a830cb3b8c8b967b23a72139700562",
"versionType": "git"
},
{
"lessThan": "6.18.40",
"status": "affected",
"version": "6.18.16",
"versionType": "semver"
},
{
"lessThan": "6.20",
"status": "affected",
"version": "6.19.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.0"
},
{
"lessThan": "7.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.40",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.40",
"versionStartIncluding": "6.18.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "7.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "7.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.19.6",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: ISST: Restore SST-PP control to all domains\n\nThe SST-PP control offset is only restored to power domain 0 after\nresume. During suspend, control values are read and stored for all\npower domains.\n\nUse pd_info-\u003esst_base instead of power_domain_info-\u003esst_base, which\nonly points to power domain 0 base address."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.1,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The flawed writeq runs only in the ISST TPMI driver PM resume callback (intel_sst_resume -\u003e tpmi_sst_dev_resume) after a local suspend-to-RAM cycle, not from any network packet handler or remote service.\nAC:L - Once a multi-domain SST-TPMI system completes S3 suspend, resume deterministically executes the wrong MMIO restore for every power domain above zero with no races or attacker-dependent timing.\nPR:L - Reaching the buggy resume handler requires only initiating a system suspend (e.g., writing mem to /sys/power/state, which lacks a CAP_SYS_ADMIN check, or polkit-permitted local suspend); user namespaces cannot grant ISST ioctl writes but can still allow this PM path.\nUI:N - Exploitation does not require a victim to open files, mount filesystems, or take any other interactive action beyond the attacker (or system policy) triggering suspend and automatic resume.\nS:U - Impact is confined to corrupting SST-PP hardware configuration and host stability on the same machine; it does not cross a VM, container, or IOMMU security boundary to another authority.\nC:N - The bug performs MMIO writeq operations to hardware registers only; it does not read kernel memory, leak pointers, or expose data to userspace.\nI:H - Each incorrect resume writes a full 64-bit SST-PP control value to the wrong hardware MMIO address, corrupting platform power/performance configuration; values can be attacker-influenced via prior CAP_SYS_ADMIN ISST perf-level changes before suspend.\nA:H - Misdirected MMIO writes can panic or hang the host, and unrestored or corrupted SST-PP settings on additional power domains can destabilize multi-die Xeon systems after every affected resume cycle."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:40:51.234Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/cea03d67db3a880893360bdbb1b0b8d9b33b1799"
},
{
"url": "https://git.kernel.org/stable/c/2a42f651cce91e9cbe65fe933622c522cbb1868b"
},
{
"url": "https://git.kernel.org/stable/c/2565a28cdcdcb035e151d285efcba26bccb3726e"
}
],
"title": "platform/x86: ISST: Restore SST-PP control to all domains",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72143",
"datePublished": "2026-08-15T05:53:16.241Z",
"dateReserved": "2026-08-09T03:40:39.908Z",
"dateUpdated": "2026-10-16T18:44:58.966Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…