{"uuid": "68b2aae6-32ef-4faf-89f0-31a68ce6dcc4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47715", "type": "seen", "source": "https://t.me/cvedetector/8477", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47715 - ZyXEL EX5700 WiFi mt76 Kernel Oops Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47715 \nPublished : Oct. 21, 2024, 12:15 p.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: mt76: mt7915: fix oops on non-dbdc mt7986  \n  \nmt7915_band_config() sets band_idx = 1 on the main phy for mt7986  \nwith MT7975_ONE_ADIE or MT7976_ONE_ADIE.  \n  \nCommit 0335c034e726 (\"wifi: mt76: fix race condition related to  \nchecking tx queue fill status\") introduced a dereference of the  \nphys array indirectly indexed by band_idx via wcid->phy_idx in  \nmt76_wcid_cleanup(). This caused the following Oops on affected  \nmt7986 devices:  \n  \n Unable to handle kernel read from unreadable memory at virtual address 0000000000000024  \n Mem abort info:  \n   ESR = 0x0000000096000005  \n   EC = 0x25: DABT (current EL), IL = 32 bits  \n   SET = 0, FnV = 0  \n   EA = 0, S1PTW = 0  \n   FSC = 0x05: level 1 translation fault  \n Data abort info:  \n   ISV = 0, ISS = 0x00000005  \n   CM = 0, WnR = 0  \n user pgtable: 4k pages, 39-bit VAs, pgdp=0000000042545000  \n [0000000000000024] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000  \n Internal error: Oops: 0000000096000005 [#1] SMP  \n Modules linked in: ... mt7915e mt76_connac_lib mt76 mac80211 cfg80211 ...  \n CPU: 2 PID: 1631 Comm: hostapd Not tainted 5.15.150 #0  \n Hardware name: ZyXEL EX5700 (Telenor) (DT)  \n pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \n pc : mt76_wcid_cleanup+0x84/0x22c [mt76]  \n lr : mt76_wcid_cleanup+0x64/0x22c [mt76]  \n sp : ffffffc00a803700  \n x29: ffffffc00a803700 x28: ffffff80008f7300 x27: ffffff80003f3c00  \n x26: ffffff80000a7880 x25: ffffffc008c26e00 x24: 0000000000000001  \n x23: ffffffc000a68114 x22: 0000000000000000 x21: ffffff8004172cc8  \n x20: ffffffc00a803748 x19: ffffff8004152020 x18: 0000000000000000  \n x17: 00000000000017c0 x16: ffffffc008ef5000 x15: 0000000000000be0  \n x14: ffffff8004172e28 x13: ffffff8004172e28 x12: 0000000000000000  \n x11: 0000000000000000 x10: ffffff8004172e30 x9 : ffffff8004172e28  \n x8 : 0000000000000000 x7 : ffffff8004156020 x6 : 0000000000000000  \n x5 : 0000000000000031 x4 : 0000000000000000 x3 : 0000000000000001  \n x2 : 0000000000000000 x1 : ffffff80008f7300 x0 : 0000000000000024  \n Call trace:  \n  mt76_wcid_cleanup+0x84/0x22c [mt76]  \n  __mt76_sta_remove+0x70/0xbc [mt76]  \n  mt76_sta_state+0x8c/0x1a4 [mt76]  \n  mt7915_eeprom_get_power_delta+0x11e4/0x23a0 [mt7915e]  \n  drv_sta_state+0x144/0x274 [mac80211]  \n  sta_info_move_state+0x1cc/0x2a4 [mac80211]  \n  sta_set_sinfo+0xaf8/0xc24 [mac80211]  \n  sta_info_destroy_addr_bss+0x4c/0x6c [mac80211]  \n  \n  ieee80211_color_change_finish+0x1c08/0x1e70 [mac80211]  \n  cfg80211_check_station_change+0x1360/0x4710 [cfg80211]  \n  genl_family_rcv_msg_doit+0xb4/0x110  \n  genl_rcv_msg+0xd0/0x1bc  \n  netlink_rcv_skb+0x58/0x120  \n  genl_rcv+0x34/0x50  \n  netlink_unicast+0x1f0/0x2ec  \n  netlink_sendmsg+0x198/0x3d0  \n  ____sys_sendmsg+0x1b0/0x210  \n  ___sys_sendmsg+0x80/0xf0  \n  __sys_sendmsg+0x44/0xa0  \n  __arm64_sys_sendmsg+0x20/0x30  \n  invoke_syscall.constprop.0+0x4c/0xe0  \n  do_el0_svc+0x40/0xd0  \n  el0_svc+0x14/0x4c  \n  el0t_64_sync_handler+0x100/0x110  \n  el0t_64_sync+0x15c/0x160  \n Code: d2800002 910092c0 52800023 f9800011 (885f7c01)  \n ---[ end trace 7e42dd9a39ed2281 ]---  \n  \nFix by using mt76_dev_phy() which will map band_idx to the correct phy  \nfor all hardware combinations. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T15:10:39.000000Z"}