GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2026-68469 (GCVE-0-2026-68469)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:51 – Updated: 2026-08-17 05:06
VLAI
Title
wifi: mwifiex: fix permanently busy scans after multiple roam iterations
Summary
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: fix permanently busy scans after multiple roam iterations In order for the firmware to sleep, the driver has to confirm a previously received sleep request. The normal sequence of evets goes like this: EVENT_SLEEP -> adapter->ps_state = PS_STATE_PRE_SLEEP -> sleep-confirm -> SLEEP -> EVENT_AWAKE -> AWAKE. Before sending the sleep-confirm command, the driver must make sure there are no commands either running or waiting to be completed. mwifiex_ret_802_11_associate() unconditionally sets ps_state = PS_STATE_AWAKE when it processes the association command response, outside of the normal powersave management flow. If EVENT_SLEEP arrives while the association command is in flight, ps_state is PRE_SLEEP when the association command response is parsed, and the forced AWAKE overwrites it. The deferred sleep-confirm is never sent. A subsequent scan_start command is correctly acknowledged, but the firmware doesn't generate scan_result events. The scan request never finishes, and additional requests from userspace fail with -EBUSY. After testing on both IW412 and W8997, I could only trigger the bug on the IW412 and observed the firmwares behave differently. On the IW412 the firmware still sends EVENT_SLEEP while the authentication / association process is ongoing. A W8997 under the same conditions seems to suppress power-save for the duration of the association, so PRE_SLEEP never coincided with the association response even after extended periods of testing using the loops described below (>12hours). On the IW412, the delay between commands that triggers an EVENT_SLEEP was empirically determined to be ~20ms. This delay can naturally occur when the driver is outputting debugging information (debug_mask = 0x00000037), in which situation the busy scans issue is repeatable while running "test 1)" as described below. If the delay between commands is less than ~20ms, the firmware stays awake and the issue was not reproducible running the same test. The host_mlme=false path also behaves differently. In this case, the entire authentication / association transaction is executed by one command (HostCmd_CMD_802_11_ASSOCIATE), and the firmware doesn't emit EVENT_SLEEP while the command is running. Remove the assignment so the ps_state is only manipulated in the paths that are related to powersave event handling and on the main workqueue for correct sleep confirmation. The following loop tests were performed (with debugging output enabled): 1) force roaming between two AP's, one 5GHz and one 2.4GHz, same SSID. Use wpa_cli to trigger the roaming behavior, sleep 2s between iterations. 2) force a disconnection to AP 1 and a connection to AP 2, test scan. Use wpa_cli to trigger the connection changes, sleep 2s between iterations. Each test ran in each device for at least 3 hours.
Severity
No CVSS data available.
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < 2ed36b2586f16c480ed58de303af704c2235e16d (git)
Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < 5796eabe435d83544b6fe39851ce47ca68fdb778 (git)
Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < 31a2c409f8f58d20f0f6391c151421155768ed77 (git)
Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < deb5f0ae384f1cf41fccaf6375266db2f2911b2b (git)
Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < 1bc55db2d34756bd53e4460dbb699619ee13cd7f (git)
Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < a59cfa165aee3e29d06145041c0ebe46a51de604 (git)
Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < 6126e12bf8c87badeab41a164c9689ac88e5c160 (git)
Affected: 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e , < d78a407bad6f500884a8606aea1a5a9207be4030 (git)
guessed Create a notification for this product.
Linux Linux Affected: 3.0
Unaffected: 0 , < 3.0 (semver)
Unaffected: 5.10.261 , ≤ 5.10.* (semver)
Unaffected: 5.15.212 , ≤ 5.15.* (semver)
Unaffected: 6.1.178 , ≤ 6.1.* (semver)
Unaffected: 6.6.145 , ≤ 6.6.* (semver)
Unaffected: 6.12.97 , ≤ 6.12.* (semver)
Unaffected: 6.18.40 , ≤ 6.18.* (semver)
Unaffected: 7.1.5 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/wireless/marvell/mwifiex/join.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2ed36b2586f16c480ed58de303af704c2235e16d",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            },
            {
              "lessThan": "5796eabe435d83544b6fe39851ce47ca68fdb778",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            },
            {
              "lessThan": "31a2c409f8f58d20f0f6391c151421155768ed77",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            },
            {
              "lessThan": "deb5f0ae384f1cf41fccaf6375266db2f2911b2b",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            },
            {
              "lessThan": "1bc55db2d34756bd53e4460dbb699619ee13cd7f",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            },
            {
              "lessThan": "a59cfa165aee3e29d06145041c0ebe46a51de604",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            },
            {
              "lessThan": "6126e12bf8c87badeab41a164c9689ac88e5c160",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            },
            {
              "lessThan": "d78a407bad6f500884a8606aea1a5a9207be4030",
              "status": "affected",
              "version": "5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/wireless/marvell/mwifiex/join.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "3.0"
            },
            {
              "lessThan": "3.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.261",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.212",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.178",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.145",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.97",
              "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": "5.10.261",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.212",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.178",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.145",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.97",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.40",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mwifiex: fix permanently busy scans after multiple roam iterations\n\nIn order for the firmware to sleep, the driver has to confirm a\npreviously received sleep request. The normal sequence of evets goes\nlike this:\nEVENT_SLEEP -\u003e adapter-\u003eps_state = PS_STATE_PRE_SLEEP -\u003e sleep-confirm\n-\u003e SLEEP -\u003e EVENT_AWAKE -\u003e AWAKE.\nBefore sending the sleep-confirm command, the driver must make sure\nthere are no commands either running or waiting to be completed.\n\nmwifiex_ret_802_11_associate() unconditionally sets\nps_state = PS_STATE_AWAKE when it processes the association command\nresponse, outside of the normal powersave management flow. If\nEVENT_SLEEP arrives while the association command is in flight,\nps_state is PRE_SLEEP when the association command response is parsed,\nand the forced AWAKE overwrites it. The deferred sleep-confirm is\nnever sent.\n\nA subsequent scan_start command is correctly acknowledged, but the\nfirmware doesn\u0027t generate scan_result events. The scan request never\nfinishes, and additional requests from userspace fail with -EBUSY.\n\nAfter testing on both IW412 and W8997, I could only trigger the bug on\nthe IW412 and observed the firmwares behave differently. On the IW412\nthe firmware still sends EVENT_SLEEP while the authentication /\nassociation process is ongoing. A W8997 under the same\nconditions seems to suppress power-save for the duration of the\nassociation, so PRE_SLEEP never coincided with the association response\neven after extended periods of testing using the loops\ndescribed below (\u003e12hours).\n\nOn the IW412, the delay between commands that triggers an EVENT_SLEEP\nwas empirically determined to be ~20ms. This delay can naturally occur\nwhen the driver is outputting debugging information\n(debug_mask = 0x00000037), in which situation the busy scans issue is\nrepeatable while running \"test 1)\" as described below. If the delay\nbetween commands is less than ~20ms, the firmware stays awake and\nthe issue was not reproducible running the same test.\n\nThe host_mlme=false path also behaves differently. In this case, the\nentire authentication / association transaction is executed by one\ncommand (HostCmd_CMD_802_11_ASSOCIATE), and the firmware doesn\u0027t emit\nEVENT_SLEEP while the command is running.\n\nRemove the assignment so the ps_state is only manipulated in the paths\nthat are related to powersave event handling and on the main workqueue\nfor correct sleep confirmation.\n\nThe following loop tests were performed (with debugging output enabled):\n1) force roaming between two AP\u0027s, one 5GHz and one 2.4GHz, same\nSSID. Use wpa_cli to trigger the roaming behavior, sleep 2s\nbetween iterations.\n2) force a disconnection to AP 1 and a connection to AP 2, test\nscan. Use wpa_cli to trigger the connection changes, sleep 2s\nbetween iterations.\n\nEach test ran in each device for at least 3 hours."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:06:11.253Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d"
        },
        {
          "url": "https://git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778"
        },
        {
          "url": "https://git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77"
        },
        {
          "url": "https://git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b"
        },
        {
          "url": "https://git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f"
        },
        {
          "url": "https://git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604"
        },
        {
          "url": "https://git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160"
        },
        {
          "url": "https://git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030"
        }
      ],
      "title": "wifi: mwifiex: fix permanently busy scans after multiple roam iterations",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-68469",
    "datePublished": "2026-08-15T05:51:27.429Z",
    "dateReserved": "2026-07-30T09:28:09.396Z",
    "dateUpdated": "2026-08-17T05:06:11.253Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-68469",
      "date": "2026-09-05",
      "epss": "0.00212",
      "percentile": "0.11426"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-68469\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-08-15T06:19:57.620\",\"lastModified\":\"2026-08-17T06:17:56.250\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nwifi: mwifiex: fix permanently busy scans after multiple roam iterations\\n\\nIn order for the firmware to sleep, the driver has to confirm a\\npreviously received sleep request. The normal sequence of evets goes\\nlike this:\\nEVENT_SLEEP -\u003e adapter-\u003eps_state = PS_STATE_PRE_SLEEP -\u003e sleep-confirm\\n-\u003e SLEEP -\u003e EVENT_AWAKE -\u003e AWAKE.\\nBefore sending the sleep-confirm command, the driver must make sure\\nthere are no commands either running or waiting to be completed.\\n\\nmwifiex_ret_802_11_associate() unconditionally sets\\nps_state = PS_STATE_AWAKE when it processes the association command\\nresponse, outside of the normal powersave management flow. If\\nEVENT_SLEEP arrives while the association command is in flight,\\nps_state is PRE_SLEEP when the association command response is parsed,\\nand the forced AWAKE overwrites it. The deferred sleep-confirm is\\nnever sent.\\n\\nA subsequent scan_start command is correctly acknowledged, but the\\nfirmware doesn\u0027t generate scan_result events. The scan request never\\nfinishes, and additional requests from userspace fail with -EBUSY.\\n\\nAfter testing on both IW412 and W8997, I could only trigger the bug on\\nthe IW412 and observed the firmwares behave differently. On the IW412\\nthe firmware still sends EVENT_SLEEP while the authentication /\\nassociation process is ongoing. A W8997 under the same\\nconditions seems to suppress power-save for the duration of the\\nassociation, so PRE_SLEEP never coincided with the association response\\neven after extended periods of testing using the loops\\ndescribed below (\u003e12hours).\\n\\nOn the IW412, the delay between commands that triggers an EVENT_SLEEP\\nwas empirically determined to be ~20ms. This delay can naturally occur\\nwhen the driver is outputting debugging information\\n(debug_mask = 0x00000037), in which situation the busy scans issue is\\nrepeatable while running \\\"test 1)\\\" as described below. If the delay\\nbetween commands is less than ~20ms, the firmware stays awake and\\nthe issue was not reproducible running the same test.\\n\\nThe host_mlme=false path also behaves differently. In this case, the\\nentire authentication / association transaction is executed by one\\ncommand (HostCmd_CMD_802_11_ASSOCIATE), and the firmware doesn\u0027t emit\\nEVENT_SLEEP while the command is running.\\n\\nRemove the assignment so the ps_state is only manipulated in the paths\\nthat are related to powersave event handling and on the main workqueue\\nfor correct sleep confirmation.\\n\\nThe following loop tests were performed (with debugging output enabled):\\n1) force roaming between two AP\u0027s, one 5GHz and one 2.4GHz, same\\nSSID. Use wpa_cli to trigger the roaming behavior, sleep 2s\\nbetween iterations.\\n2) force a disconnection to AP 1 and a connection to AP 2, test\\nscan. Use wpa_cli to trigger the connection changes, sleep 2s\\nbetween iterations.\\n\\nEach test ran in each device for at least 3 hours.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/net/wireless/marvell/mwifiex/join.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"2ed36b2586f16c480ed58de303af704c2235e16d\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"5796eabe435d83544b6fe39851ce47ca68fdb778\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"31a2c409f8f58d20f0f6391c151421155768ed77\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"deb5f0ae384f1cf41fccaf6375266db2f2911b2b\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"1bc55db2d34756bd53e4460dbb699619ee13cd7f\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"a59cfa165aee3e29d06145041c0ebe46a51de604\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"6126e12bf8c87badeab41a164c9689ac88e5c160\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e\",\"lessThan\":\"d78a407bad6f500884a8606aea1a5a9207be4030\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/net/wireless/marvell/mwifiex/join.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"3.0\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"3.0\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.10.261\",\"lessThanOrEqual\":\"5.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.212\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.178\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.145\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12.97\",\"lessThanOrEqual\":\"6.12.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.40\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1.5\",\"lessThanOrEqual\":\"7.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.2\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-08-19T05:26:34+00:00",
      "cve": "CVE-2026-68469",
      "id": "CVE-2026-68469",
      "initial_release_date": "2026-08-15T00:00:00+00:00",
      "product_status:known_affected": "260",
      "product_status:known_not_affected": "14",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: wifi: mwifiex: fix permanently busy scans after multiple roam iterations",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-68469.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…