Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Wi-Fi driver flaw in Intel iwlwifi MLD handling. A scheduled scan-start task may continue after disconnection and run after related interface memory is no longer valid, risking kernel memory corruption. The CVSS score is high, but the listed attack vector is local and requires low privileges.
Executive priority
Treat as a high-priority kernel maintenance issue for Linux fleets with Intel Wi-Fi exposure. It is not currently evidenced as internet-exploited from the provided sources, but successful local exploitation could compromise the kernel. Patch through standard OS channels as soon as vendor updates are available.
Technical view
The mlo_scan_start_wk work item is not canceled on disconnection. If queued work runs after drv_change_interface or after the vif is freed, it can cause init-after-queue behavior or use-after-free in the Linux iwlwifi MLD code path. The CVE is associated with CWE-772 and CVSS 3.1 score 7.8.
Likely exposure
Systems are most likely exposed when running affected Linux kernel versions with Intel iwlwifi MLD Wi-Fi functionality present and usable. Headless servers or systems without the relevant Intel Wi-Fi driver path are less likely to be practically exposed, but package-level exposure should still be checked against vendor advisories.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. CVSS indicates local access, low attack complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact. Public exploit status is not established by the provided sources.
Researcher notes
Focus validation on the iwlwifi MLD workqueue lifecycle around disconnection, drv_change_interface, and vif teardown. The provided description identifies missing cancellation of mlo_scan_start_wk as the root cause. Avoid claiming remote reachability or weaponized exploitation without additional evidence.
Mitigation direction
- Apply vendor kernel updates that include the referenced stable Linux fixes.
- Track Red Hat and Linux distribution advisories for fixed package versions.
- Prioritize laptops, workstations, and appliances using Intel iwlwifi Wi-Fi.
- Where acceptable, disable unused Wi-Fi functionality until patched.
- Do not infer fixed versions beyond vendor-published guidance.
Validation and detection
- Inventory Linux kernel versions across affected endpoints and appliances.
- Check whether Intel iwlwifi hardware and driver functionality are present.
- Compare installed kernel packages against distribution advisories and stable commit references.
- Confirm patch deployment through vendor package metadata or release notes.
- Review crash telemetry for kernel oopses involving iwlwifi MLD paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-772: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23185 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
6.7MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Reported to Red Hat.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-14T00:00:00.000Z: Reported to Red Hat.
- 2026-02-14T00:00:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/9b9f52f052f4953fecd2190ae2dde3aa76d10962CVE reference, Linux
- https://git.kernel.org/stable/c/5ff641011ab7fb63ea101251087745d9826e8ef5CVE reference, Linux
- https://access.redhat.com/security/cve/CVE-2026-23185CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2439925CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23185.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Resource after Effective Lifetime
Missing Release of Resource after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.