LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39750: wifi: ath12k: Correct tid cleanup when tid setup fails

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Correct tid cleanup when tid setup fails Currently, if any error occurs during ath12k_dp_rx_peer_tid_setup(), the tid value is already incremented, even though the corresponding TID is not actually allocated. Proceed to ath12k_dp_rx_peer_tid_delete() starting from unallocated tid, which might leads to freeing unallocated TID and cause potential crash or out-of-bounds access. Hence, fix by correctly decrementing tid before cleanup to match only the successfully allocated TIDs. Also, remove tid-- from failure case of ath12k_dp_rx_peer_frag_setup(), as decrementing the tid before cleanup in loop will take care of this. Compile tested only.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux ath12k Wi-Fi driver cleanup error can release a traffic identifier that was never allocated when setup fails. This may crash the system or access memory outside the intended bounds. Systems without the affected driver path are not exposed.

Executive priority

Treat as a high-priority kernel update for endpoints or appliances actively using ath12k around untrusted wireless participants. Prioritize verification before emergency-wide action because exposure depends on driver use, affected code, and vendor backport status, while exploitation is not reported.

Technical view

During ath12k_dp_rx_peer_tid_setup() failure handling, the TID counter points beyond successfully allocated entries. Cleanup then calls ath12k_dp_rx_peer_tid_delete() for an unallocated TID, creating potential invalid freeing, out-of-bounds access, or a kernel crash. The correction decrements the counter before cleanup and adjusts fragment-setup failure handling.

Likely exposure

Exposure is limited to Linux systems using the affected ath12k Wi-Fi driver and vulnerable kernel code. The supplied CVSS vector indicates adjacent-network reachability without privileges or user interaction. The source bundle's version data is irregular, so distributions and backports require individual verification.

Exploitation context

The bundle provides no evidence of active exploitation, and the CVE is not identified as KEV. Although CVSS scores confidentiality, integrity, and availability impacts as high, the description specifically establishes only potential crashing or out-of-bounds access. A reliable attacker-controlled trigger is not documented.

Researcher notes

The failure occurs specifically during rollback after TID setup errors. The fix aligns cleanup with successfully allocated TIDs. The upstream description says the change was compile-tested only, leaving runtime validation evidence incomplete. Supplied affected-version entries include unusual values and do not establish reliable continuous ranges.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable stable fix or distribution backport.
  • Prioritize systems actively using ath12k on networks accessible to untrusted nearby devices.
  • Consult Linux distribution advisories to resolve ambiguous affected-version and backport status.
  • If immediate updating is impossible, reduce exposure of affected wireless interfaces where operationally acceptable.

Validation and detection

  • Inventory Linux kernel versions and determine whether the ath12k driver is present and active.
  • Confirm the installed kernel includes the applicable referenced fix or an equivalent vendor backport.
  • Review kernel and wireless-driver logs for ath12k crashes or memory-access faults.
  • Test updated kernels with representative ath12k connectivity and failure conditions before broad deployment.
Prepared
Confidence
medium
Sources
7

Public sources used

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-2025-39750 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-39750Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd889913205cf7ebda905b1e62c5867ed4e39f6c2, d889913205cf7ebda905b1e62c5867ed4e39f6c2, d889913205cf7ebda905b1e62c5867ed4e39f6c2, d889913205cf7ebda905b1e62c5867ed4e39f6c2, d889913205cf7ebda905b1e62c5867ed4e39f6c2unaffected
LinuxLinux6.3, 0, 6.6.103, 6.12.43, 6.15.11, 6.16.2, 6.17affected
Weakness

CWE details

No CWE listed

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