Files
vuln-cve/data/2026/64xxx/CVE-2026-64176.json
T

223 lines
12 KiB
JSON

{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-64176",
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"state": "PUBLISHED",
"assignerShortName": "Linux",
"dateReserved": "2026-07-19T07:54:57.039Z",
"datePublished": "2026-07-19T15:41:00.830Z",
"dateUpdated": "2026-10-19T20:28:14.591Z"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux",
"dateUpdated": "2026-08-05T12:39:54.477Z"
},
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix driver-set TX rates on old devices\n\nOn old devices such as 7265D, rates are still encoded in version 1\nformat, which doesn't use the CCK/OFDM rate index (0-3/0-7) but\nrather their PLCP value (e.g. 10 for 1 Mbps CCK rate.)\n\nWhile introducing v3 rates, I changed the driver from internally\nhandling v1 rates and converting to v2, to internally handling v3\nand converting to v1 or v2 according to the firmware. I accordingly\nchanged the code in iwl_mvm_mac80211_idx_to_hwrate() to no longer\nhave different values for different APIs. This was correct.\n\nHowever, I later reverted this part of the change, because it was\nreported that I had broken beacon rates, causing a FW assert/crash.\nThis caused TX_CMD rates to be set incorrectly, potentially causing\na warning when reported back from the device as having been used.\n\nFix this (hopefully correctly now) by handling beacon rates in the\nTX_CMD that's embedded in the beacon template command separately.\nRestore iwl_mvm_mac80211_idx_to_hwrate() to return only the rate\nindex, not PLCP value, fixing the real TX_CMD."
}
],
"metrics": [
{
"cvssV3_1": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"baseScore": 8.1,
"baseSeverity": "HIGH"
},
"scenarios": [
{
"lang": "en",
"value": "AV:A - The vulnerable TX rate path is reached when the iwlwifi driver transmits WiFi management frames (probe responses, auth/assoc) or beacon templates in response to over-the-air activity. A remote attacker on the same WiFi/BSS segment can trigger this by sending probe requests to a victim AP or operating a rogue AP that causes victim clients to exchange management frames.\nAC:L - Once the victim uses affected legacy Intel hardware (e.g. 7265D with v1 rate firmware), the attacker can reliably trigger the bug by sending standard 802.11 management frames; no special timing, memory layout, or race conditions beyond normal WiFi traffic are required.\nPR:N - An adjacent attacker needs no privileges on the victim system. Exploitation is triggered purely by WiFi frames received by the victim's wireless interface; no local account, CAP_NET_ADMIN, or ioctl/netlink access on the victim is required.\nUI:N - From the attacker's perspective, no action by the victim user is needed beyond the WiFi interface being active (e.g., an AP broadcasting beacons or a client performing normal association). Probe responses and association handshakes are sent automatically by the driver.\nS:U - The vulnerability is confined to the iwlwifi kernel driver and its firmware interaction on the victim host. Impact does not cross a security boundary such as VM escape, sandbox escape, or IOMMU bypass.\nC:H - The double PLCP conversion passes PLCP values (e.g. 55, 110 for CCK rates) as array indices to iwl_fw_rate_idx_to_plcp(), which performs an unchecked lookup into a ~17-element table, causing out-of-bounds kernel memory reads whose results are embedded into TX commands.\nI:N - The bug corrupts rate-encoding metadata sent to firmware but does not provide an arbitrary kernel write, use-after-free, or demonstrated control-flow hijack primitive. Impact is malformed TX parameters and firmware misbehavior, not integrity of arbitrary kernel or user data.\nA:H - The fix commit and prior bug report document firmware assert/crash from incorrect beacon/TX_CMD rates on old devices, and the RX path emits WARN_ON for invalid rate values reported back from firmware. This can disable WiFi connectivity and potentially cause repeated firmware restart loops."
}
]
}
],
"affected": [
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "unaffected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c",
"drivers/net/wireless/intel/iwlwifi/mvm/utils.c"
],
"versions": [
{
"version": "3592c0083fb29cca13cd9978b8844d58b4eff548",
"lessThan": "6fe92651b44fd3cfc8dcfdaad0e82885c384dada",
"status": "affected",
"versionType": "git"
},
{
"version": "3592c0083fb29cca13cd9978b8844d58b4eff548",
"lessThan": "6b58a79f2cd98156856eb49e8b55db5facdd7e6d",
"status": "affected",
"versionType": "git"
},
{
"version": "3592c0083fb29cca13cd9978b8844d58b4eff548",
"lessThan": "fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b",
"status": "affected",
"versionType": "git"
},
{
"version": "c6c14c2b08e9c4c82e1ec39ef3e8b9ec845ac7fd",
"status": "affected",
"versionType": "git"
},
{
"version": "6.17.9",
"lessThan": "6.18",
"status": "affected",
"versionType": "semver"
}
]
},
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "affected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c",
"drivers/net/wireless/intel/iwlwifi/mvm/utils.c"
],
"versions": [
{
"version": "6.18",
"status": "affected"
},
{
"version": "0",
"lessThan": "6.18",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.18.34",
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "7.0.11",
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "7.1",
"lessThanOrEqual": "*",
"status": "unaffected",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.18",
"versionEndExcluding": "6.18.34"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.18",
"versionEndExcluding": "7.0.11"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.18",
"versionEndExcluding": "7.1"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.17.9"
}
]
}
]
}
],
"references": [
{
"url": "https://git.kernel.org/stable/c/6fe92651b44fd3cfc8dcfdaad0e82885c384dada"
},
{
"url": "https://git.kernel.org/stable/c/6b58a79f2cd98156856eb49e8b55db5facdd7e6d"
},
{
"url": "https://git.kernel.org/stable/c/fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b"
}
],
"title": "wifi: iwlwifi: mvm: fix driver-set TX rates on old devices",
"x_generator": {
"engine": "bippy-1.2.0"
}
},
"adp": [
{
"metrics": [
{
"other": {
"type": "ssvc",
"content": {
"id": "CVE-2026-64176",
"role": "CISA Coordinator",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2026-10-16T15:37:13.733939Z"
}
}
}
],
"problemTypes": [
{
"descriptions": [
{
"lang": "en",
"type": "CWE",
"cweId": "CWE-682",
"description": "CWE-682 Incorrect Calculation"
}
]
}
],
"title": "CISA ADP Vulnrichment",
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-10-19T20:28:14.591Z"
}
}
]
}
}