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-2025-21636sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The 'net' structure can be obtained from the table->data using container_of(). Note that table->data could also be used directly, as this is the only member needed from the 'net' structure, but that would increase the size of this fix, to use '*data' everywhere 'net->sctp.probe_interval' is used.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 16 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

CVSS scores of CVE-2025-21636, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.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.22% · top 87% of all CVEs (16 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 d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 – < 1dc5da6c4178f3e4b95c631418f72de9f86c0449
    • affected d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 – < 44ee8635922b6eb940faddb961a8347c6857d722
    • affected d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 – < 284a221f8fa503628432c7bb5108277c688c6ffa
    • affected d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 – < bcf8c60074e81ed2ac2d35130917175a3949c917
    • affected d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 – < 6259d2484d0ceff42245d1f09cc8cb6ee72d847a
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.177 – ≤ 5.15.*
    • unaffected 6.1.125 – ≤ 6.1.*
    • unaffected 6.6.72 – ≤ 6.6.*
    • unaffected 6.12.10 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .