Skip to content
Fencer Intel
medium 5.5

CVE-2023-52527 json

ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()

published 2y ago modified 5mo ago also EUVD-2023-57152

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 4.14.327, 4.19.296, 5.4.258, 5.10.198, 5.15.135, 6.1.57, 6.5.7, 6.6
  • linux Debian 12 6.1.64-1
  • linux Debian 14, Debian 13 6.5.8-1

debian advisories DEBIAN-CVE-2023-52527

  • linux Ubuntu 20.04 LTS 5.4.0-171.189
  • linux Ubuntu 22.04 LTS 5.15.0-94.104
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1118.128
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1053.58
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1122.131
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1051.59
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1050.55
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1065.70

ubuntu advisories UBUNTU-CVE-2023-52527

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-syms SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.219.1
  • kernel-source SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.219.1
  • kernel-default SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +2 more 4.12.14-122.219.1
  • kernel-obs-build SLE Software Development Kit 12 SP5 4.12.14-122.219.1
  • kernel-rt SLE Real Time 12 SP5 4.12.14-10.188.1
  • kernel-syms-rt SLE Real Time 12 SP5 4.12.14-10.188.1
  • kernel-rt_debug SLE Real Time 12 SP5 4.12.14-10.188.1
  • kernel-source-rt SLE Real Time 12 SP5 4.12.14-10.188.1

suse advisories SUSE-SU-2024:2184-1SUSE-SU-2024:1983-1SUSE-SU-2024:1979-1

Is CVE-2023-52527 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-52527 updated cvss 5.3

kernel: ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-20).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.