Bug 2379219 (CVE-2025-38292) - CVE-2025-38292 kernel: wifi: ath12k: fix invalid access to memory
Summary: CVE-2025-38292 kernel: wifi: ath12k: fix invalid access to memory
Keywords:
Status: NEW
Alias: CVE-2025-38292
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-10 08:04 UTC by OSIDB Bzimport
Modified: 2025-10-06 13:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:13598 0 None None None 2025-08-11 10:08:44 UTC
Red Hat Product Errata RHSA-2025:13602 0 None None None 2025-08-11 10:59:41 UTC

Description OSIDB Bzimport 2025-07-10 08:04:13 UTC
In the Linux kernel, the following vulnerability has been resolved:

wifi: ath12k: fix invalid access to memory

In ath12k_dp_rx_msdu_coalesce(), rxcb is fetched from skb and boolean
is_continuation is part of rxcb.
Currently, after freeing the skb, the rxcb->is_continuation accessed
again which is wrong since the memory is already freed.
This might lead use-after-free error.

Hence, fix by locally defining bool is_continuation from rxcb,
so that after freeing skb, is_continuation can be used.

Compile tested only.

Comment 1 Avinash Hanwate 2025-07-11 07:10:52 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025071011-CVE-2025-38292-e03a@gregkh/T

Comment 4 errata-xmlrpc 2025-08-11 10:08:43 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:13598 https://access.redhat.com/errata/RHSA-2025:13598

Comment 5 errata-xmlrpc 2025-08-11 10:59:39 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:13602 https://access.redhat.com/errata/RHSA-2025:13602


Note You need to log in before you can comment on or make changes to this bug.