LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23133: wifi: ath10k: fix dma_free_coherent() pointer

In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: fix dma_free_coherent() pointer dma_alloc_coherent() allocates a DMA mapped buffer and stores the addresses in XXX_unaligned fields. Those should be reused when freeing the buffer rather than the aligned addresses.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Wi-Fi driver defect in ath10k involving the wrong pointer being used when freeing DMA memory. The public bundle does not describe a proven security impact, CVSS score, or active exploitation. Treat it as a kernel maintenance risk for systems using the affected driver, not as an emergency based on current evidence.

Executive priority

Handle through normal kernel patch management unless internal exposure shows ath10k use on sensitive systems. The current public record lacks severity, exploit evidence, and impact detail, so urgency should be driven by asset exposure and vendor package availability.

Technical view

The fix changes ath10k DMA cleanup to free the DMA buffer using the unaligned address returned by dma_alloc_coherent(), rather than the later aligned address. Passing the wrong pointer to dma_free_coherent() can corrupt driver memory-management assumptions. The source bundle names Linux kernel versions and stable commits but does not provide impact details or exploitability analysis.

Likely exposure

Exposure is most likely on Linux systems that use the ath10k Wi-Fi driver and run affected kernel builds. Servers without this driver or hardware are less likely exposed. The bundle’s version data is incomplete and should be reconciled against vendor kernel packages.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit code, or attacker prerequisites. It also does not define whether exploitation is local, remote, or merely a crash condition. Avoid assuming real-world exploitability beyond the kernel fix.

Researcher notes

Useful follow-up is branch mapping: identify exactly which stable commits correspond to each maintained Linux series and whether downstream distributors backported the fix under their own version numbers. The source bundle does not include CVSS, CWE, trigger conditions, or security impact classification.

Mitigation direction

  • Update to a vendor kernel build containing the referenced stable fix.
  • Prioritize systems that load the ath10k Wi-Fi driver.
  • Check Linux distribution advisories for branch-specific fixed package versions.
  • If no vendor package exists, follow kernel stable guidance for the relevant branch.

Validation and detection

  • Inventory hosts running Linux kernels in the affected range.
  • Check whether the ath10k driver is present or loaded.
  • Compare installed kernel packages against vendor advisories for CVE-2026-23133.
  • Confirm the relevant stable commit is included in the running kernel source or changelog.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2026-23133 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2a1e1ad3fd37a632b61f50e73dafddb4b0fa57f1, 2a1e1ad3fd37a632b61f50e73dafddb4b0fa57f1, 2a1e1ad3fd37a632b61f50e73dafddb4b0fa57f1, 2a1e1ad3fd37a632b61f50e73dafddb4b0fa57f1, 2a1e1ad3fd37a632b61f50e73dafddb4b0fa57f1, 2a1e1ad3fd37a632b61f50e73dafddb4b0fa57f1, 2a1e1ad3fd37a632b61f50e73dafddb4b0fa57f1unaffected
LinuxLinux4.16, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.