CVE-2026-68469: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-mc74-x78c-h295
Share
Published
Advisory Summary

CVE-2026-68469 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68469 at a Glance

CVE Identifier CVE-2026-68469
GHSA Identifier GHSA-mc74-x78c-h295
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-68469

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-68469, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-68469 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68469
git.kernel.org/stable/c/1bc55db2d3... WEB
https://git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f
git.kernel.org/stable/c/2ed36b2586... WEB
https://git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d
git.kernel.org/stable/c/31a2c409f8... WEB
https://git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77
git.kernel.org/stable/c/5796eabe43... WEB
https://git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778
git.kernel.org/stable/c/6126e12bf8... WEB
https://git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160
git.kernel.org/stable/c/a59cfa165a... WEB
https://git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604
git.kernel.org/stable/c/d78a407bad... WEB
https://git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030
git.kernel.org/stable/c/deb5f0ae38... WEB
https://git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b

Frequently Asked Questions

What is CVE-2026-68469?
CVE-2026-68469 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68469?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68469?
CVE-2026-68469 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68469?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mc74-x78c-h295",
  "modified" : "2026-08-15T06:32:07Z",
  "published" : "2026-08-15T06:32:07Z",
  "aliases" : [ "CVE-2026-68469" ],
  "details" : "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 -> adapter->ps_state = PS_STATE_PRE_SLEEP -> sleep-confirm\n-> SLEEP -> EVENT_AWAKE -> 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't 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 (>12hours).\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't 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's, 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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68469"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:19:57Z"
  }
}