# CVE-2023-52527: linux: In the Linux kernel, the following vulnerability has been resolved:  ipv4, ipv6: Fix handling of transhdrlen in __ip{...

CVE-2023-52527 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-52527, released March 2, 2024. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2023-52527
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0024
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Mar 2, 2024

## Description

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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 6.1.64-1 | [DEBIAN-CVE-2023-52527](https://patchblox.com/security/data/fix/linux/debian-cve-2023-52527.md) | Mar 2, 2024 |
| Linux | linux Debian 13.5 (trixie) | 6.5.8-1 | [DEBIAN-CVE-2023-52527](https://patchblox.com/security/data/fix/linux/debian-cve-2023-52527.md) | Mar 2, 2024 |
| Linux | linux Debian 14 | 6.5.8-1 | [DEBIAN-CVE-2023-52527](https://patchblox.com/security/data/fix/linux/debian-cve-2023-52527.md) | Mar 2, 2024 |

---

Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.