aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/scripts/lib/kdoc/kdoc_output.py
diff options
context:
space:
mode:
authorQasim Ijaz <qasdev00@gmail.com>2025-05-26 19:36:07 +0100
committerJakub Kicinski <kuba@kernel.org>2025-05-28 19:10:04 -0700
commit9ad0452c0277b816a435433cca601304cfac7c21 (patch)
tree1d29e5c635496de4c75dbc0b1fa5edc6f1d98b1d /scripts/lib/kdoc/kdoc_output.py
parentFix sock_exceed_buf_limit not being triggered in __sk_mem_raise_allocated (diff)
downloadwireguard-linux-9ad0452c0277b816a435433cca601304cfac7c21.tar.xz
wireguard-linux-9ad0452c0277b816a435433cca601304cfac7c21.zip
net: ch9200: fix uninitialised access during mii_nway_restart
In mii_nway_restart() the code attempts to call mii->mdio_read which is ch9200_mdio_read(). ch9200_mdio_read() utilises a local buffer called "buff", which is initialised with control_read(). However "buff" is conditionally initialised inside control_read(): if (err == size) { memcpy(data, buf, size); } If the condition of "err == size" is not met, then "buff" remains uninitialised. Once this happens the uninitialised "buff" is accessed and returned during ch9200_mdio_read(): return (buff[0] | buff[1] << 8); The problem stems from the fact that ch9200_mdio_read() ignores the return value of control_read(), leading to uinit-access of "buff". To fix this we should check the return value of control_read() and return early on error. Reported-by: syzbot <syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com> Closes: https://syzkaller.appspot.com/bug?extid=3361c2d6f78a3e0892f9 Tested-by: syzbot <syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com> Fixes: 4a476bd6d1d9 ("usbnet: New driver for QinHeng CH9200 devices") Cc: stable@vger.kernel.org Signed-off-by: Qasim Ijaz <qasdev00@gmail.com> Link: https://patch.msgid.link/20250526183607.66527-1-qasdev00@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions