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-2026-74735l2tp: fix tunnel and session refcount leak on seq_file release

Description

In the Linux kernel, the following vulnerability has been resolved: l2tp: fix tunnel and session refcount leak on seq_file release In pppol2tp_proc_open() and l2tp_dfs_seq_open(), iteration state (pd->tunnel and pd->session) is kept in seq_file private data to allow iteration across multiple read() system calls. However, if userspace closes /proc/net/pppol2tp or /sys/kernel/debug/l2tp/tunnels before reading to end-of-file (EOF), any tunnel or session reference stored in pd->tunnel / pd->session is left un-dropped when seq_file private data is freed. Fix this by dropping any remaining pd->tunnel and pd->session references in pppol2tp_proc_release() and l2tp_dfs_seq_release() when closing the file.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0e0c3fee3a59a387aeecc4fca6f3a2e9615a5443 – < c38b723858a51d6ca4e56470b9f1087f23276772
    • affected 0e0c3fee3a59a387aeecc4fca6f3a2e9615a5443 – < bd897e414451fb34dfdf08b31899180e5ab7149b
    • affected 0e0c3fee3a59a387aeecc4fca6f3a2e9615a5443 – < bdf83613781956cc39798ed08321f74ab0467f4d
    • affected 0e0c3fee3a59a387aeecc4fca6f3a2e9615a5443 – < 8c4fde01bcf91f22b9c7ded8c3e14addd7ddd500
    • affected 0e0c3fee3a59a387aeecc4fca6f3a2e9615a5443 – < ebe2774e956482dd3c70b8991f6f7654356339e6
    • affected 0e0c3fee3a59a387aeecc4fca6f3a2e9615a5443 – < 9006c116dd111d457bf5d074990210f70a4ad2c8
    • affected f6104e9ae04462523c372928b1173766a771ef95
    • affected 7f8e401f9e612df2a95c1ef76217c00181389bb5
    • affected c712ed63e9b33d9a282fbd92ce25c64918c3129f
    • affected 9a8863e8a8def9d88583cd9c60db38a008e6b8cf
    • affected 3.16.60 – < 3.17
    • affected 4.16.6 – < 4.17
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .