| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations. |
| Memory corruption when processing draw objects of incorrect type during graphics command list execution. |
| Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization. |
| Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed. |
| Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms. |
| Memory Corruption when processing camera CRE driver operations with improper handling of buffer limits during hardware update preparation. |
| Memory corruption when processing command buffer requests with invalid length parameters in the Android Camera driver. |
| Memory corruption when processing camera requests with excessive batch and IO buffer configurations exceeds allocated memory size. |
| Memory corruption when non-secure loader rewrites page tables before secure memory initialization. |
| Memory corruption while processing IOCTL command called from user space to the kernel with invalid parameters. |
| Transient DOS when processing authentication frames with invalid FILS information element header lengths. |
| Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled. |
| Memory Corruption when processing I2C transfer requests due to a race condition between memory allocation and data copying. |
| Cryptographic Issue while processing registration requests with malformed or missing authentication parameters. |
| Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration. |
| Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values. |
| Information Disclosure when IPSec negotiation fails or is not established properly during NG-eCall SIP signaling. |
| Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities. |
| Memory corruption while processing a packet with a size close to the maximum allowed value. |
| In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: fix node corruption in ar->arvifs list
In current WLAN recovery code flow, ath11k_core_halt() only
reinitializes the "arvifs" list head. This will cause the
list node immediately following the list head to become an
invalid list node. Because the prev of that node still points
to the list head "arvifs", but the next of the list head "arvifs"
no longer points to that list node.
When a WLAN recovery occurs during the execution of a vif
removal, and it happens before the spin_lock_bh(&ar->data_lock)
in ath11k_mac_op_remove_interface(), list_del() will detect the
previously mentioned situation, thereby triggering a kernel panic.
The fix is to remove and reinitialize all vif list nodes from the
list head "arvifs" during WLAN halt. The reinitialization is to make
the list nodes valid, ensuring that the list_del() in
ath11k_mac_op_remove_interface() can execute normally.
Call trace:
__list_del_entry_valid_or_report+0xb8/0xd0
ath11k_mac_op_remove_interface+0xb0/0x27c [ath11k]
drv_remove_interface+0x48/0x194 [mac80211]
ieee80211_do_stop+0x6e0/0x844 [mac80211]
ieee80211_stop+0x44/0x17c [mac80211]
__dev_close_many+0xac/0x150
__dev_change_flags+0x194/0x234
dev_change_flags+0x24/0x6c
devinet_ioctl+0x3a0/0x670
inet_ioctl+0x200/0x248
sock_do_ioctl+0x60/0x118
sock_ioctl+0x274/0x35c
__arm64_sys_ioctl+0xac/0xf0
invoke_syscall+0x48/0x114
...
Tested-on: QCA6698AQ hw2.1 PCI WLAN.HSP.1.1-04591-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1 |
