Unknown

CVE-2026-90107 — net/smc: free pending qentry in smc_llc_flow_stop() before memset

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.

Published Sep 17, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.21%

ahead of 11% of scored CVEs · Oct 19, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 555da9af827d95134656fa459c8f3ece04dd867a and < 8e3deb150a5237b672c4579e69a6deb02027dbed≥ 555da9af827d95134656fa459c8f3ece04dd867a and < 11bc373ee6630709f0c2da2e7860c23d503c9e9d≥ 555da9af827d95134656fa459c8f3ece04dd867a and < 032aec7d03c9102616b98fea74f8f7145e7f867c≥ 555da9af827d95134656fa459c8f3ece04dd867a and < 957dba2b8b5aebfe09caa6a6b22b958079082eab≥ 555da9af827d95134656fa459c8f3ece04dd867a and < f03aa5d36ae3c4068a1c3885146be99aa7fd9307≥ 555da9af827d95134656fa459c8f3ece04dd867a and < 0879ea157acc1ac6752f6fcb755d1f91a2359238≥ 555da9af827d95134656fa459c8f3ece04dd867a and < 5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b≥ 555da9af827d95134656fa459c8f3ece04dd867a and < 5ee0ceddc7785c6dcf4a8107fef01f0414a354f4 and 1 more version 5.8	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 19, 2026 · 4 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 17, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

git.kernel.org/stable/c/032aec7d03c9102616b98fea74f8f7145e7f867c
NIST National Vulnerability Database
git.kernel.org/stable/c/5ee0ceddc7785c6dcf4a8107fef01f0414a354f4
NIST National Vulnerability Database
git.kernel.org/stable/c/8e3deb150a5237b672c4579e69a6deb02027dbed
NIST National Vulnerability Database
git.kernel.org/stable/c/5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b
NIST National Vulnerability Database
git.kernel.org/stable/c/957dba2b8b5aebfe09caa6a6b22b958079082eab
NIST National Vulnerability Database
git.kernel.org/stable/c/f03aa5d36ae3c4068a1c3885146be99aa7fd9307
NIST National Vulnerability Database
github.com/advisories/GHSA-mw8r-cvfc-f297
GitHub Security Advisories
git.kernel.org/stable/c/0879ea157acc1ac6752f6fcb755d1f91a2359238
NIST National Vulnerability Database
git.kernel.org/stable/c/11bc373ee6630709f0c2da2e7860c23d503c9e9d
NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2026-90107
GitHub Security Advisories

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 1d
Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 1d
Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-90107 is "net/smc: free pending qentry in smc_llc_flow_stop() before memset", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.