6.6 CVE-2025-59615

Enriched by CISA Patch
 

Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization.
https://nvd.nist.gov/vuln/detail/CVE-2025-59615

Categories

CWE-416 : Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. If the product accesses a previously-freed pointer, then it means that a separate weakness or error already occurred previously, such as a race condition, an unexpected or poorly handled error condition, confusion over which part of the program is responsible for freeing the memory, performing the free too soon, etc. a pointer that no longer points to valid memory, often after it has been freed commonly used acronym for Use After Free Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues. Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) Use tools that are integrated duringcompilation to insert runtime error-checking mechanismsrelated to memory safety errors, such as AddressSanitizer(ASan) for C/C++ [REF-1518]. Choose a language that provides automatic memory management. When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy. TCP/IP code for an OS has a use-after-free that can leak heap memory contents Chain: an operating system kernel has insufficent resource locking (CWE-413) leading to a use after free (CWE-416). Chain: two threads in a web browser use the same resource (CWE-366), but one of those threads can destroy the resource before the other has completed (CWE-416). Chain: mobile platform race condition (CWE-362) leading to use-after-free (CWE-416), as exploited in the wild per CISA KEV. Chain: race condition (CWE-362) leads to use-after-free (CWE-416), as exploited in the wild per CISA KEV. Use-after-free triggered by closing a connection while data is still being transmitted. Improper allocation for invalid data leads to use-after-free. certificate with a large number of Subject Alternate Names not properly handled in realloc, leading to use-after-free Timers are not disabled when a related object is deleted Access to a "dead" object that is being cleaned up object is deleted even with a non-zero reference count, and later accessed use-after-free involving request containing an invalid version number unload of an object that is currently being accessed by other functionality incorrectly tracking a reference count leads to use-after-free use-after-free related to use of uninitialized memory HTML document with incorrectly-nested tags Use after free in ActiveX object by providing a malformed argument to a method use-after-free by disconnecting during data transfer, or a message containing incorrect data types disconnect during a large data transfer causes incorrect reference count, leading to use-after-free use-after-free found by fuzzing Chain: race condition (CWE-362) from improper handling of a page transition in web client while an applet is loading (CWE-368) leads to use after free (CWE-416) realloc generates new buffer and pointer, but previous pointer is still retained, leading to use after free Use-after-free in web browser, probably resultant from not initializing memory. use-after-free when one thread accessed memory that was freed by another thread assignment of malformed values to certain properties triggers use after free mail server does not properly handle a long header. chain: integer overflow leads to use-after-free freed pointer dereference Chain: A multi-threaded race condition (CWE-367) allows attackers to cause two threads to process the same RPC request, which causes a use-after-free (CWE-416) in one thread

References

product-security@qualcomm.com Patch


 

AFFECTED (from MITRE)

Vendor Product Versions
Qualcomm, Inc. Snapdragon
  • FastConnect 6700 [affected]
  • FastConnect 6900 [affected]
  • FastConnect 7800 [affected]
  • Molokai [affected]
  • Orne [affected]
  • Pandeiro [affected]
  • QCM5430 [affected]
  • QCM6490 [affected]
  • QLN1083BD [affected]
  • QLN1086BD [affected]
  • QMP1000 [affected]
  • QMP2001 [affected]
  • QPA1083BD [affected]
  • QPA1086BD [affected]
  • Qualcomm Video Collaboration VC3 Platform [affected]
  • QXM1093 [affected]
  • QXM1094 [affected]
  • QXM1095 [affected]
  • QXM1096 [affected]
  • SC8380XP [affected]
  • SD865 5G [affected]
  • SM6850 [affected]
  • SM8845P [affected]
  • Snapdragon 460 Mobile Platform [affected]
  • Snapdragon 662 Mobile Platform [affected]
  • Snapdragon 8 Elite Gen 5 [affected]
  • Snapdragon AR1 Gen 1 Platform [affected]
  • Snapdragon XR2 5G Platform [affected]
  • Snapdragon XR2+ Gen 1 Platform [affected]
  • SXR2230P [affected]
  • SXR2250P [affected]
  • SXR2330P [affected]
  • SXR2350P [affected]
  • WCD9370 [affected]
  • WCD9375 [affected]
  • WCD9378 [affected]
  • WCD9380 [affected]
  • WCD9385 [affected]
  • WCD9395 [affected]
  • WCN3950 [affected]
  • WCN3988 [affected]
  • WCN6450 [affected]
  • WCN7760 [affected]
  • WCN7860 [affected]
  • WCN7861 [affected]
  • WCN7880 [affected]
  • WCN7881 [affected]
  • WSA8810 [affected]
  • WSA8815 [affected]
  • WSA8830 [affected]
  • WSA8832 [affected]
  • WSA8835 [affected]
  • WSA8840 [affected]
  • WSA8845 [affected]
  • WSA8845H [affected]
  • WSA8850 [affected]
  • WSA8850W [affected]
  • WSA8855C [affected]
  • XRV7209 [affected]
  • XRV9209 [affected]
© 2022 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.

CPE

cpe start end
Configuration 1
AND
   cpe:2.3:o:qualcomm:fastconnect_6700_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:fastconnect_6700:-:*:*:*:*:*:*:*
Configuration 2
AND
   cpe:2.3:o:qualcomm:fastconnect_6900_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:fastconnect_6900:-:*:*:*:*:*:*:*
Configuration 3
AND
   cpe:2.3:o:qualcomm:fastconnect_7800_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:fastconnect_7800:-:*:*:*:*:*:*:*
Configuration 4
AND
   cpe:2.3:o:qualcomm:molokai_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:molokai:-:*:*:*:*:*:*:*
Configuration 5
AND
   cpe:2.3:o:qualcomm:orne_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:orne:-:*:*:*:*:*:*:*
Configuration 6
AND
   cpe:2.3:o:qualcomm:pandeiro_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:pandeiro:-:*:*:*:*:*:*:*
Configuration 7
AND
   cpe:2.3:o:qualcomm:qcm5430_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qcm5430:-:*:*:*:*:*:*:*
Configuration 8
AND
   cpe:2.3:o:qualcomm:qcm6490_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qcm6490:-:*:*:*:*:*:*:*
Configuration 9
AND
   cpe:2.3:o:qualcomm:qln1083bd_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qln1083bd:-:*:*:*:*:*:*:*
Configuration 10
AND
   cpe:2.3:o:qualcomm:qln1086bd_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qln1086bd:-:*:*:*:*:*:*:*
Configuration 11
AND
   cpe:2.3:o:qualcomm:qmp1000_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qmp1000:-:*:*:*:*:*:*:*
Configuration 12
AND
   cpe:2.3:o:qualcomm:qmp2001_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qmp2001:-:*:*:*:*:*:*:*
Configuration 13
AND
   cpe:2.3:o:qualcomm:qpa1083bd_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qpa1083bd:-:*:*:*:*:*:*:*
Configuration 14
AND
   cpe:2.3:o:qualcomm:qpa1086bd_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qpa1086bd:-:*:*:*:*:*:*:*
Configuration 15
AND
   cpe:2.3:o:qualcomm:video_collaboration_vc3_platform_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:video_collaboration_vc3_platform:-:*:*:*:*:*:*:*
Configuration 16
AND
   cpe:2.3:o:qualcomm:qxm1093_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qxm1093:-:*:*:*:*:*:*:*
Configuration 17
AND
   cpe:2.3:o:qualcomm:qxm1094_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qxm1094:-:*:*:*:*:*:*:*
Configuration 18
AND
   cpe:2.3:o:qualcomm:qxm1095_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qxm1095:-:*:*:*:*:*:*:*
Configuration 19
AND
   cpe:2.3:o:qualcomm:qxm1096_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:qxm1096:-:*:*:*:*:*:*:*
Configuration 20
AND
   cpe:2.3:o:qualcomm:sc8380xp_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sc8380xp:-:*:*:*:*:*:*:*
Configuration 21
AND
   cpe:2.3:o:qualcomm:sd865_5g_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sd865_5g:-:*:*:*:*:*:*:*
Configuration 22
AND
   cpe:2.3:o:qualcomm:sm6850_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sm6850:-:*:*:*:*:*:*:*
Configuration 23
AND
   cpe:2.3:o:qualcomm:sm8845p_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sm8845p:-:*:*:*:*:*:*:*
Configuration 24
AND
   cpe:2.3:o:qualcomm:snapdragon_460_mobile_platform_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:snapdragon_460_mobile_platform:-:*:*:*:*:*:*:*
Configuration 25
AND
   cpe:2.3:o:qualcomm:snapdragon_662_mobile_platform_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:snapdragon_662_mobile_platform:-:*:*:*:*:*:*:*
Configuration 26
AND
   cpe:2.3:o:qualcomm:snapdragon_8_elite_gen_5_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:snapdragon_8_elite_gen_5:-:*:*:*:*:*:*:*
Configuration 27
AND
   cpe:2.3:o:qualcomm:snapdragon_ar1_gen_1_platform_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:snapdragon_ar1_gen_1_platform:-:*:*:*:*:*:*:*
Configuration 28
AND
   cpe:2.3:o:qualcomm:snapdragon_xr2_5g_platform_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:snapdragon_xr2_5g_platform:-:*:*:*:*:*:*:*
Configuration 29
AND
   cpe:2.3:o:qualcomm:snapdragon_xr2+_gen_1_platform_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:snapdragon_xr2+_gen_1_platform:-:*:*:*:*:*:*:*
Configuration 30
AND
   cpe:2.3:o:qualcomm:sxr2230p_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sxr2230p:-:*:*:*:*:*:*:*
Configuration 31
AND
   cpe:2.3:o:qualcomm:sxr2250p_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sxr2250p:-:*:*:*:*:*:*:*
Configuration 32
AND
   cpe:2.3:o:qualcomm:sxr2330p_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sxr2330p:-:*:*:*:*:*:*:*
Configuration 33
AND
   cpe:2.3:o:qualcomm:sxr2350p_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:sxr2350p:-:*:*:*:*:*:*:*
Configuration 34
AND
   cpe:2.3:o:qualcomm:wcd9370_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcd9370:-:*:*:*:*:*:*:*
Configuration 35
AND
   cpe:2.3:o:qualcomm:wcd9375_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcd9375:-:*:*:*:*:*:*:*
Configuration 36
AND
   cpe:2.3:o:qualcomm:wcd9378_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcd9378:-:*:*:*:*:*:*:*
Configuration 37
AND
   cpe:2.3:o:qualcomm:wcd9380_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcd9380:-:*:*:*:*:*:*:*
Configuration 38
AND
   cpe:2.3:o:qualcomm:wcd9385_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcd9385:-:*:*:*:*:*:*:*
Configuration 39
AND
   cpe:2.3:o:qualcomm:wcd9395_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcd9395:-:*:*:*:*:*:*:*
Configuration 40
AND
   cpe:2.3:o:qualcomm:wcn3950_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn3950:-:*:*:*:*:*:*:*
Configuration 41
AND
   cpe:2.3:o:qualcomm:wcn3988_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn3988:-:*:*:*:*:*:*:*
Configuration 42
AND
   cpe:2.3:o:qualcomm:wcn6450_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn6450:-:*:*:*:*:*:*:*
Configuration 43
AND
   cpe:2.3:o:qualcomm:wcn7760_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn7760:-:*:*:*:*:*:*:*
Configuration 44
AND
   cpe:2.3:o:qualcomm:wcn7860_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn7860:-:*:*:*:*:*:*:*
Configuration 45
AND
   cpe:2.3:o:qualcomm:wcn7861_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn7861:-:*:*:*:*:*:*:*
Configuration 46
AND
   cpe:2.3:o:qualcomm:wcn7880_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn7880:-:*:*:*:*:*:*:*
Configuration 47
AND
   cpe:2.3:o:qualcomm:wcn7881_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wcn7881:-:*:*:*:*:*:*:*
Configuration 48
AND
   cpe:2.3:o:qualcomm:wsa8810_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8810:-:*:*:*:*:*:*:*
Configuration 49
AND
   cpe:2.3:o:qualcomm:wsa8815_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8815:-:*:*:*:*:*:*:*
Configuration 50
AND
   cpe:2.3:o:qualcomm:wsa8830_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8830:-:*:*:*:*:*:*:*
Configuration 51
AND
   cpe:2.3:o:qualcomm:wsa8832_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8832:-:*:*:*:*:*:*:*
Configuration 52
AND
   cpe:2.3:o:qualcomm:wsa8835_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8835:-:*:*:*:*:*:*:*
Configuration 53
AND
   cpe:2.3:o:qualcomm:wsa8840_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8840:-:*:*:*:*:*:*:*
Configuration 54
AND
   cpe:2.3:o:qualcomm:wsa8845_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8845:-:*:*:*:*:*:*:*
Configuration 55
AND
   cpe:2.3:o:qualcomm:wsa8845h_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8845h:-:*:*:*:*:*:*:*
Configuration 56
AND
   cpe:2.3:o:qualcomm:wsa8850_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8850:-:*:*:*:*:*:*:*
Configuration 57
AND
   cpe:2.3:o:qualcomm:wsa8850w_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8850w:-:*:*:*:*:*:*:*
Configuration 58
AND
   cpe:2.3:o:qualcomm:wsa8855c_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:wsa8855c:-:*:*:*:*:*:*:*
Configuration 59
AND
   cpe:2.3:o:qualcomm:xrv7209_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:xrv7209:-:*:*:*:*:*:*:*
Configuration 60
AND
   cpe:2.3:o:qualcomm:xrv9209_firmware:-:*:*:*:*:*:*:*
  Running on/with
  cpe:2.3:h:qualcomm:xrv9209:-:*:*:*:*:*:*:*

REMEDIATION

Patch

Url
https://docs.qualcomm.com/product/publicresources/securitybulletin/july-2026-...

EXPLOITS

Exploit-db.com

id description date
No known exploits

POC Github

Url
No known exploits

Other Nist (github, ...)

Url
No known exploits

CAPEC

Common Attack Pattern Enumerations and Classifications

id description severity
No entry