| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| 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 |
| Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification. |
| Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits. |
| Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization. |
| Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input due to accessing already freed memory. |
| Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input. |
| Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks. |
| Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values. |
| Memory Corruption when processing asynchronous input parameters due to improper handling of modified values between check and use. |
| Memory Corruption when allocating memory with sizes that exceed the maximum allowed value. |
| Memory Corruption when processing invalid HT40 channel layouts during dynamic channel switching operations. |
| Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security. |
| Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer. |
| Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization. |
| Information Disclosure when resetting device to factory default settings through powerline interface allows unauthorized access to device configuration. |
| Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. |
| Memory Corruption when processing device identifier strings that exceed the expected maximum length. |
| Information Disclosure when processing advertisement frames with malformed MBSSID elements of insufficient length. |
| Memory corruption in diagnostic services due to absence of input validation |
