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-46158mptcp: pm: ADD_ADDR rtx: always decrease sk refcount

Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: always decrease sk refcount When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(). It should then be released in all cases at the end. Some (unlikely) checks were returning directly instead of calling sock_put() to decrease the refcount. Jump to a new 'exit' label to call __sock_put() (which will become sock_put() in the next commit) to fix this potential leak. While at it, drop the '!msk' check which cannot happen because it is never reset, and explicitly mark the remaining one as "unlikely".

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-2026-46158, by who scored it
Scored byCVSSScoreVector
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.13% · top 98% 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 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < f5555a6d7c472849fdf2b426e3d0a85103118793
    • affected 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < e9ba34301d2e90f63f97c76ad9eb98e5250fe961
    • affected 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < 81d8142148164176385c279c7c1e1d581867423d
    • affected 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < 9426265e157dd77ec237c795901ed4dea6d69b5c
    • affected 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < b41dd76f3b9735096c21d3e799a2b9fe36498d57
    • affected 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < acd3d3562315c99f3c0db16f0fcc5f0306638982
    • affected 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < 25e37407442b8766ec2cf52fb4e31b5c3d3aeeae
    • affected 00cfd77b9063dcdf3628a7087faba60de85a9cc8 – < 9634cb35af17019baec21ca648516ce376fa10e6
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.218 – ≤ 5.15.*
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.30 – ≤ 6.18.*
    • unaffected 7.0.7 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .