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-2024-26752l2tp: pass correct message length to ip6_append_data

Description

In the Linux kernel, the following vulnerability has been resolved: l2tp: pass correct message length to ip6_append_data l2tp_ip6_sendmsg needs to avoid accounting for the transport header twice when splicing more data into an already partially-occupied skbuff. To manage this, we check whether the skbuff contains data using skb_queue_empty when deciding how much data to append using ip6_append_data. However, the code which performed the calculation was incorrect: ulen = len + skb_queue_empty(&sk->sk_write_queue) ? transhdrlen : 0; ...due to C operator precedence, this ends up setting ulen to transhdrlen for messages with a non-zero length, which results in corrupted packets on the wire. Add parentheses to correct the calculation in line with the original intent.

Timeline

  1. ID reserved

    By Linux

  2. · 44 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-2024-26752, 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.25% · top 83% of all CVEs (12 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 559d697c5d072593d22b3e0bd8b8081108aeaf59 – < 4c3ce64bc9d36ca9164dd6c77ff144c121011aae
    • affected 1fc793d68d50dee4782ef2e808913d5dd880bcc6 – < c1d3a84a67db910ce28a871273c992c3d7f9efb5
    • affected 96b2e1090397217839fcd6c9b6d8f5d439e705ed – < dcb4d14268595065c85dc5528056713928e17243
    • affected cd1189956393bf850b2e275e37411855d3bd86bb – < 0da15a70395182ee8cb75716baf00dddc0bea38d
    • affected f6a7182179c0ed788e3755ee2ed18c888ddcc33f – < 13cd1daeea848614e585b2c6ecc11ca9c8ab2500
    • affected 9d4c75800f61e5d75c1659ba201b6c0c7ead3070 – < 804bd8650a3a2bf3432375f8c97d5049d845ce56
    • affected 9d4c75800f61e5d75c1659ba201b6c0c7ead3070 – < 83340c66b498e49353530e41542500fc8a4782d6
    • affected 9d4c75800f61e5d75c1659ba201b6c0c7ead3070 – < 359e54a93ab43d32ee1bff3c2f9f10cb9f6b6e79
    • affected 7626b9fed53092aa2147978070e610ecb61af844
    • affected fe80658c08e3001c80c5533cd41abfbb0e0e28fd
    • affected 4.19.296 – < 4.19.308
    • affected 5.4.258 – < 5.4.270
    • affected 5.10.198 – < 5.10.211
    • affected 5.15.135 – < 5.15.150
    • affected 6.1.57 – < 6.1.80
    • affected 4.14.327 – < 4.15
    • affected 6.5.7 – < 6.6

  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 4.19.308 – ≤ 4.19.*
    • unaffected 5.4.270 – ≤ 5.4.*
    • unaffected 5.10.211 – ≤ 5.10.*
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.80 – ≤ 6.1.*
    • unaffected 6.6.19 – ≤ 6.6.*
    • unaffected 6.7.7 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .