First published: Sat Mar 02 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data() Including the transhdrlen in length is a problem when the packet is partially filled (e.g. something like send(MSG_MORE) happened previously) when appending to an IPv4 or IPv6 packet as we don't want to repeat the transport header or account for it twice. This can happen under some circumstances, such as splicing into an L2TP socket. The symptom observed is a warning in __ip6_append_data(): WARNING: CPU: 1 PID: 5042 at net/ipv6/ip6_output.c:1800 __ip6_append_data.isra.0+0x1be8/0x47f0 net/ipv6/ip6_output.c:1800 that occurs when MSG_SPLICE_PAGES is used to append more data to an already partially occupied skbuff. The warning occurs when 'copy' is larger than the amount of data in the message iterator. This is because the requested length includes the transport header length when it shouldn't. This can be triggered by, for example: sfd = socket(AF_INET6, SOCK_DGRAM, IPPROTO_L2TP); bind(sfd, ...); // ::1 connect(sfd, ...); // ::1 port 7 send(sfd, buffer, 4100, MSG_MORE); sendfile(sfd, dfd, NULL, 1024); Fix this by only adding transhdrlen into the length if the write queue is empty in l2tp_ip6_sendmsg(), analogously to how UDP does things. l2tp_ip_sendmsg() looks like it won't suffer from this problem as it builds the UDP packet itself.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=3.5<4.14.327 | |
Linux Kernel | >=4.15<4.19.296 | |
Linux Kernel | >=4.20<5.4.258 | |
Linux Kernel | >=5.5<5.10.198 | |
Linux Kernel | >=5.11<5.15.135 | |
Linux Kernel | >=5.16<6.1.57 | |
Linux Kernel | >=6.2<6.5.7 | |
Linux Kernel | =6.6-rc1 | |
Linux Kernel | =6.6-rc2 | |
Linux Kernel | =6.6-rc3 | |
Linux Kernel | =6.6-rc4 | |
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.11-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-52527 has a severity rating that may vary but generally affects the reliability of packet handling in the Linux kernel.
To address CVE-2023-52527, update your Linux kernel to a version that addresses this vulnerability, such as those mentioned in the remedy section.
CVE-2023-52527 affects several versions of the Linux kernel, including versions from 3.5 up to 6.6-rc4.
The potential impacts of CVE-2023-52527 include issues with packet transmission which may compromise the reliability of data communication.
Yes, CVE-2023-52527 has been publicly disclosed and identified for remediation.