CVE-2026-90107

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

CVE-2026-90107 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-90107, released September 23, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0022
12th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 12.15 (bookworm) 6.1.190-1 DEBIAN-CVE-2026-90107 Sep 23, 2026
linux · Debian 13.5 (trixie) 6.12.111-1 DEBIAN-CVE-2026-90107 Sep 23, 2026
linux · Debian 14 7.2.6-1 DEBIAN-CVE-2026-90107 Sep 23, 2026
linux-6.12 · Debian 12.15 (bookworm) 6.12.111-1~deb12u1 DEBIAN-CVE-2026-90107 Sep 23, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.