Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-52527, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < 7626b9fed53092aa2147978070e610ecb61af844
    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < 559d697c5d072593d22b3e0bd8b8081108aeaf59
    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < 1fc793d68d50dee4782ef2e808913d5dd880bcc6
    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < 96b2e1090397217839fcd6c9b6d8f5d439e705ed
    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < cd1189956393bf850b2e275e37411855d3bd86bb
    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < f6a7182179c0ed788e3755ee2ed18c888ddcc33f
    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < fe80658c08e3001c80c5533cd41abfbb0e0e28fd
    • affected a32e0eec7042b21ccb52896cf715e3e2641fed93 – < 9d4c75800f61e5d75c1659ba201b6c0c7ead3070
  • Linux · Linux

    • affected 3.5
    • unaffected < 3.5
    • unaffected 4.14.327 – ≤ 4.14.*
    • unaffected 4.19.296 – ≤ 4.19.*
    • unaffected 5.4.258 – ≤ 5.4.*
    • unaffected 5.10.198 – ≤ 5.10.*
    • unaffected 5.15.135 – ≤ 5.15.*
    • unaffected 6.1.57 – ≤ 6.1.*
    • unaffected 6.5.7 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52527 badge
[![CVE-2023-52527](https://cveledger.app/badge/CVE-2023-52527.svg)](https://cveledger.app/cve/CVE-2023-52527)

Record last updated .