CVE-2026-68403
Vulnerability Scoring
Analysis In Progress
CVE-2026-68403 Vulnerability Analysis & Exploit Details
CVE-2026-68403
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2026-68403 Details
Status: Received on 10 Aug 2026, 13:20 UTC
Last updated: 🕔 19 Aug 2026, 17:20 UTC
Originally published on: 🕐 10 Aug 2026, 13:20 UTC
Time between publication and last update: 9 days
CVSS Release:
CVE-2026-68403 Vulnerability Summary
CVE-2026-68403: In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: initialize SDIO data work before cleanup brcmf_sdio_probe() stores the newly allocated bus in sdiodev->bus before allocating the ordered workqueue. If that allocation fails, the function jumps to fail and calls brcmf_sdio_remove(). brcmf_sdio_remove() unconditionally cancels bus->datawork. Initialize the work item before the first failure path that can reach brcmf_sdio_remove(), so the cleanup path always observes a valid work object. This issue was found by our static analysis tool and then confirmed by manual review of the probe error path and the remove-time work drain. The problem pattern is an early setup failure that reaches a cleanup helper which cancels an embedded work item before its initializer has run. A QEMU PoC forced alloc_ordered_workqueue() to fail at the same point in brcmf_sdio_probe(), before INIT_WORK(&bus->datawork) is reached. The resulting fail path calls brcmf_sdio_remove(), and DEBUG_OBJECTS reports the invalid work drain with brcmf_sdio_probe() and brcmf_sdio_remove() in the stack.
Assessing the Risk of CVE-2026-68403
Access Complexity Graph
The exploitability of CVE-2026-68403 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2026-68403
No exploitability data is available for CVE-2026-68403.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2026-68403, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2026-68403, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2026-68403 does not compromise confidentiality.
-
Integrity:
None
CVE-2026-68403 does not impact data integrity.
-
Availability:
None
CVE-2026-68403 does not affect system availability.
CVE-2026-68403 References
External References
- https://git.kernel.org/stable/c/2a665946e0407a05a3f81bd56a08553c446498e0
- https://git.kernel.org/stable/c/5c342437ea44bb829680ca9e4f683dd5b325b219
- https://git.kernel.org/stable/c/6bd21ec8549a5854dd64204a66289952917a924c
- https://git.kernel.org/stable/c/860887d22890417d43ef8298f0cc4865e29b54de
- https://git.kernel.org/stable/c/9a4be91e5bb032b34cb3c962f6d4f82e7ef09364
- https://git.kernel.org/stable/c/c73c3fc1c7ca5a927639f0884624cb244ba791e4
- https://git.kernel.org/stable/c/f50a2b9e57a751e70ae9a272875d80d39eaccd6a
- https://git.kernel.org/stable/c/fb12c87ae855346321af72e57a93c146205f1090
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2026-68403: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2026-90555 – vLLM versions before 0.28.0 fail to validate audio sample rate headers in the transcription endpoint, allowing authenticated clients to bypass dura...
- CVE-2026-90554 – vLLM versions >=0.10.2 and <0.28.0 do not apply any audio decode-size or duration limit when extracting audio from video input for NanoNemotronVL m...
- CVE-2026-90553 – vLLM before 0.28.0 contains a remote code execution vulnerability in the LlavaOnevision2 processor loader that ignores the trust_remote_code parame...
- CVE-2026-90552 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the Playlists_schedules/list.json.php a...
- CVE-2026-90551 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the video_from_program API endpoint, al...