DEBIAN-CVE-2022-50701

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host SDIO may need addtional 511 bytes to align bus operation. If the tailroom of this skb is not big enough, we would access invalid memory region. For low level operation, increase skb size to keep valid memory access in SDIO host. Error message: [69.951] BUG: KASAN: slab-out-of-bounds in sgcopybuffer+0xe9/0x1a0 [69.951] Read of size 64 at addr ffff88811c9cf000 by task kworker/u16:7/451 [69.951] CPU: 4 PID: 451 Comm: kworker/u16:7 Tainted: G W OE 6.1.0-rc5 #1 [69.951] Workqueue: kvub300c vub300cmndworkthread [vub300] [69.951] Call Trace: [69.951] <TASK> [69.952] dumpstacklvl+0x49/0x63 [69.952] printreport+0x171/0x4a8 [69.952] kasanreport+0xb4/0x130 [69.952] kasancheckrange+0x149/0x1e0 [69.952] memcpy+0x24/0x70 [69.952] sgcopybuffer+0xe9/0x1a0 [69.952] sgcopytobuffer+0x12/0x20 [69.952] _commandwritedata.isra.0+0x23c/0xbf0 [vub300] [69.952] vub300cmndworkthread+0x17f3/0x58b0 [vub300] [69.952] processonework+0x7ee/0x1320 [69.952] workerthread+0x53c/0x1240 [69.952] kthread+0x2b8/0x370 [69.952] retfromfork+0x1f/0x30 [69.952] </TASK> [69.952] Allocated by task 854: [69.952] kasansavestack+0x26/0x50 [69.952] kasansettrack+0x25/0x30 [69.952] kasansaveallocinfo+0x1b/0x30 [69.952] _kasankmalloc+0x87/0xa0 [69.952] _kmallocnodetrackcaller+0x63/0x150 [69.952] kmallocreserve+0x31/0xd0 [69.952] _allocskb+0xfc/0x2b0 [69.952] _mt76mcumsgalloc+0xbf/0x230 [mt76] [69.952] mt76mcusendandgetmsg+0xab/0x110 [mt76] [69.952] _mt76mcusendfirmware.cold+0x94/0x15d [mt76] [69.952] mt76connacmcusendramfirmware+0x415/0x54d [mt76connaclib] [69.952] mt76connac2loadram.cold+0x118/0x4bc [mt76connaclib] [69.952] mt7921runfirmware.cold+0x2e9/0x405 [mt7921common] [69.952] mt7921smcuinit+0x45/0x80 [mt7921s] [69.953] mt7921initwork+0xe1/0x2a0 [mt7921common] [69.953] processonework+0x7ee/0x1320 [69.953] workerthread+0x53c/0x1240 [69.953] kthread+0x2b8/0x370 [69.953] retfrom_fork+0x1f/0x30 [69.953] The buggy address belongs to the object at ffff88811c9ce800 which belongs to the cache kmalloc-2k of size 2048 [69.953] The buggy address is located 0 bytes to the right of 2048-byte region [ffff88811c9ce800, ffff88811c9cf000) [69.953] Memory state around the buggy address: [69.953] ffff88811c9cef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [69.953] ffff88811c9cef80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [69.953] >ffff88811c9cf000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [69.953] ^ [69.953] ffff88811c9cf080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [69.953] ffff88811c9cf100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc