CVE-2026-90107

net/smc: free pending qentry in smc_llc_flow_stop() before memset

N/A
Published: September 17, 2026 at 04:06 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.8555da9af827d95134656fa459c8f3ece04dd867a
Vendor states this is fixed in 032aec7d03c9102616b98fea74f8f7145e7f867c (fixed)
Vendor states this is fixed in 0879ea157acc1ac6752f6fcb755d1f91a2359238 (fixed)
Vendor states this is fixed in 11bc373ee6630709f0c2da2e7860c23d503c9e9d (fixed)
Vendor states this is fixed in 5ee0ceddc7785c6dcf4a8107fef01f0414a354f4 (fixed)
Vendor states this is fixed in 5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b (fixed)
Vendor states this is fixed in 8e3deb150a5237b672c4579e69a6deb02027dbed (fixed)
Vendor states this is fixed in 957dba2b8b5aebfe09caa6a6b22b958079082eab (fixed)
Vendor states this is fixed in f03aa5d36ae3c4068a1c3885146be99aa7fd9307 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card