CVE-2026-90107

CVE CVE-2026-90107EUVD EUVD-2026-81700Published 2026-09-17T16:06:16.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 5.15.221; 555da9af827d95134656fa459c8f3ece04dd867a <0879ea157acc1ac6752f6fcb755d1f91a2359238; patch: 6.12.110; patch: 6.6.157; 555da9af827d95134656fa459c8f3ece04dd867a <5ee0ceddc7785c6dcf4a8107fef01f0414a354f4; patch: 6.1.188; 555da9af827d95134656fa459c8f3ece04dd867a <032aec7d03c9102616b98fea74f8f7145e7f867c; 555da9af827d95134656fa459c8f3ece04dd867a <957dba2b8b5aebfe09caa6a6b22b958079082eab; 5.8; patch: 7.2.6; patch: 7.3-rc1; patch: 6.18.52; patch: 0; 555da9af827d95134656fa459c8f3ece04dd867a <5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b; patch: 5.10.270; 555da9af827d95134656fa459c8f3ece04dd867a <f03aa5d36ae3c4068a1c3885146be99aa7fd9307; 555da9af827d95134656fa459c8f3ece04dd867a <8e3deb150a5237b672c4579e69a6deb02027dbed; 555da9af827d95134656fa459c8f3ece04dd867a <11bc373ee6630709f0c2da2e7860c23d503c9e9d

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.