FKIE_CVE-2026-90136
Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-09-17 17:17
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
platform/x86/amd/hsmp: Reject negative power cap writes in hwmon
hsmp_hwmon_write() takes the user-supplied hwmon value as a signed long
and assigns "val / MICROWATT_PER_MILLIWATT" to msg.args[0], which is a
__u32. MICROWATT_PER_MILLIWATT is an unsigned long, so a negative write
to power1_cap (e.g. "echo -1 > power1_cap") is first converted to a huge
unsigned value by the division and then stored into the u32 argument.
As a result a nonsensical, multi-gigawatt socket power limit is sent to
the SMU via HSMP_SET_SOCKET_POWER_LIMIT instead of the write being
rejected.
Reject negative values with -EINVAL before the conversion.
Tested with HSMP enabled:
CAP=$(dirname $(grep -l amd_hsmp_hwmon \
/sys/class/hwmon/hwmon*/name | head -1))/power1_cap
# negative write
echo -1000000 > $CAP ; echo "ret=$?"
# valid positive write must still work
echo 400000000 > $CAP ; echo "ret=$?"
Before:
# echo -1000000 > $CAP ; echo "ret=$?"
ret=0 <- accepted; bogus limit sent to SMU
# echo 400000000 > $CAP ; echo "ret=$?"
ret=0
After:
# echo -1000000 > $CAP ; echo "ret=$?"
bash: echo: write error: Invalid argument
ret=1 <- rejected with -EINVAL
# echo 400000000 > $CAP ; echo "ret=$?"
ret=0 <- valid write still works
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/amd/hsmp/hwmon.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2c09cadec116eba3fdbcb5d8d8641f6777d4a11f",
"status": "affected",
"version": "92c025db52bb94a032eb3d473bb81e62c19ddbd3",
"versionType": "git"
},
{
"lessThan": "1b0a3d915320f1600e5ff43f8bc21b73118480b8",
"status": "affected",
"version": "92c025db52bb94a032eb3d473bb81e62c19ddbd3",
"versionType": "git"
},
{
"lessThan": "3921bb8635ff2836622df1cdf3194d4f3c1835a4",
"status": "affected",
"version": "92c025db52bb94a032eb3d473bb81e62c19ddbd3",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/platform/x86/amd/hsmp/hwmon.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.16"
},
{
"lessThan": "6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"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/amd/hsmp: Reject negative power cap writes in hwmon\n\nhsmp_hwmon_write() takes the user-supplied hwmon value as a signed long\nand assigns \"val / MICROWATT_PER_MILLIWATT\" to msg.args[0], which is a\n__u32. MICROWATT_PER_MILLIWATT is an unsigned long, so a negative write\nto power1_cap (e.g. \"echo -1 \u003e power1_cap\") is first converted to a huge\nunsigned value by the division and then stored into the u32 argument.\n\nAs a result a nonsensical, multi-gigawatt socket power limit is sent to\nthe SMU via HSMP_SET_SOCKET_POWER_LIMIT instead of the write being\nrejected.\n\nReject negative values with -EINVAL before the conversion.\n\nTested with HSMP enabled:\n\n CAP=$(dirname $(grep -l amd_hsmp_hwmon \\\n /sys/class/hwmon/hwmon*/name | head -1))/power1_cap\n\n # negative write\n echo -1000000 \u003e $CAP ; echo \"ret=$?\"\n # valid positive write must still work\n echo 400000000 \u003e $CAP ; echo \"ret=$?\"\n\nBefore:\n # echo -1000000 \u003e $CAP ; echo \"ret=$?\"\n ret=0 \u003c- accepted; bogus limit sent to SMU\n # echo 400000000 \u003e $CAP ; echo \"ret=$?\"\n ret=0\n\nAfter:\n # echo -1000000 \u003e $CAP ; echo \"ret=$?\"\n bash: echo: write error: Invalid argument\n ret=1 \u003c- rejected with -EINVAL\n # echo 400000000 \u003e $CAP ; echo \"ret=$?\"\n ret=0 \u003c- valid write still works"
}
],
"id": "CVE-2026-90136",
"lastModified": "2026-09-17T17:17:06.173",
"metrics": {},
"published": "2026-09-17T17:17:06.173",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/1b0a3d915320f1600e5ff43f8bc21b73118480b8"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2c09cadec116eba3fdbcb5d8d8641f6777d4a11f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3921bb8635ff2836622df1cdf3194d4f3c1835a4"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
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…