aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/usb/lan78xx.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2021-08-25 10:43:22 +0100
committerDavid S. Miller <davem@davemloft.net>2021-08-25 10:43:22 +0100
commitfbd029df29c6701a2df02ec69923caef5811eabd (patch)
tree78bec8033b05c8976faf0356bd48c12c94732c8f /drivers/net/usb/lan78xx.c
parentqed: Enable automatic recovery on error condition. (diff)
parentxen/netfront: don't trust the backend response data blindly (diff)
downloadlinux-dev-fbd029df29c6701a2df02ec69923caef5811eabd.tar.xz
linux-dev-fbd029df29c6701a2df02ec69923caef5811eabd.zip
Merge branch 'xen-harden-netfront'
Juergen Gross says: ==================== xen: harden netfront against malicious backends Xen backends of para-virtualized devices can live in dom0 kernel, dom0 user land, or in a driver domain. This means that a backend might reside in a less trusted environment than the Xen core components, so a backend should not be able to do harm to a Xen guest (it can still mess up I/O data, but it shouldn't be able to e.g. crash a guest by other means or cause a privilege escalation in the guest). Unfortunately netfront in the Linux kernel is fully trusting its backend. This series is fixing netfront in this regard. It was discussed to handle this as a security problem, but the topic was discussed in public before, so it isn't a real secret. It should be mentioned that a similar series has been posted some years ago by Marek Marczykowski-Górecki, but this series has not been applied due to a Xen header not having been available in the Xen git repo at that time. Additionally my series is fixing some more DoS cases. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/usb/lan78xx.c')
0 files changed, 0 insertions, 0 deletions