CVE-2026-72143 (GCVE-0-2026-72143)
Vulnerability from cvelistv5
Published
2026-08-15 05:53
Modified
2026-08-17 05:40
Severity ?
VLAI Severity ?
EPSS score ?
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.
References
Impacted products
{
"containers": {
"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-08-17T05:40:51.234Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…