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-90107net/smc: free pending qentry in smc_llc_flow_stop() before memset

Description

In the Linux kernel, the following vulnerability has been resolved: net/smc: free pending qentry in smc_llc_flow_stop() before memset smc_llc_flow_stop() resets a flow struct with a blind memset: spin_lock_bh(&lgr->llc_flow_lock); memset(flow, 0, sizeof(*flow)); flow->type = SMC_LLC_FLOW_NONE; spin_unlock_bh(&lgr->llc_flow_lock); If flow->qentry is non-NULL at this point the pointer is overwritten without the allocation being freed, leaking one kmalloc object. A late-arriving duplicate CONFIRM_LINK or ADD_LINK_CONT message can set flow->qentry after the legitimate message has been consumed by the waiter via smc_llc_flow_qentry_clr() (which NULLs the pointer but leaves flow->type non-zero) but before the flow completes and smc_llc_flow_stop() runs. In that window the duplicate is stashed into flow->qentry, and then lost when smc_llc_flow_stop() zeros the struct. Call smc_llc_flow_qentry_del() inside the lock before the memset. smc_llc_flow_qentry_del() already checks flow->qentry before freeing, so the normal case where no entry is pending is a no-op.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days 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.22% · top 88% of all CVEs (13 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 555da9af827d95134656fa459c8f3ece04dd867a – < 8e3deb150a5237b672c4579e69a6deb02027dbed
    • affected 555da9af827d95134656fa459c8f3ece04dd867a – < 11bc373ee6630709f0c2da2e7860c23d503c9e9d
    • affected 555da9af827d95134656fa459c8f3ece04dd867a – < 032aec7d03c9102616b98fea74f8f7145e7f867c
    • affected 555da9af827d95134656fa459c8f3ece04dd867a – < 957dba2b8b5aebfe09caa6a6b22b958079082eab
    • affected 555da9af827d95134656fa459c8f3ece04dd867a – < f03aa5d36ae3c4068a1c3885146be99aa7fd9307
    • affected 555da9af827d95134656fa459c8f3ece04dd867a – < 0879ea157acc1ac6752f6fcb755d1f91a2359238
    • affected 555da9af827d95134656fa459c8f3ece04dd867a – < 5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b
    • affected 555da9af827d95134656fa459c8f3ece04dd867a – < 5ee0ceddc7785c6dcf4a8107fef01f0414a354f4
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .