In the Linux kernel, the following vulnerability has been resolved: net: skbuff: don't leave stale…

Why it is Amber

• CVSS 7.5 high
• Remotely exploitable without logging in
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/39d1a6b601831237c6038b5e3ac8dbb883c1700a
• https://git.kernel.org/stable/c/5551399751e2c9f31e4f3428040985a07e79d9c2
• https://git.kernel.org/stable/c/5f19b9cfff79508e8cb09be40d014cb0807f3854
• https://git.kernel.org/stable/c/ab9414ed70bd783e902a85c350620dee269bcb2b

Original description

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: don't leave stale bytes in skb_copy_and_csum_bits() When skb_copy_and_csum_bits() reaches unreadable frags it returns 0 after copying only the linear part, and the rest of the caller's buffer is left as it was. The callers copy into a buffer that is about to go out on the wire: an ICMP error quoting the offending packet, or a driver's TX bounce buffer in skb_copy_and_csum_dev(). Neither buffer is zeroed beforehand, so whatever was in memory there gets sent. Zero the part of the buffer we didn't fill. The checksum usually won't match the data any more, so the receiver will usually drop the packet, but either way it no longer carries anything it shouldn't. Only zero for a positive @len, a negative one from a broken caller must not turn into a huge memset().