CVE-2026-74719net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler() The SMC_LLC_CONFIRM_LINK / SMC_LLC_ADD_LINK_CONT branch in smc_llc_event_handler() stores an incoming qentry into the local LLC flow without first checking whether a qentry is already pending. If a malicious or buggy peer sends a second CONFIRM_LINK or ADD_LINK_CONT request while a flow is active and flow->qentry is already set, smc_llc_flow_qentry_set() overwrites the pointer without freeing the previous allocation, leaking one kmalloc-96 object per spurious message. The sibling SMC_LLC_DELETE_LINK branch already has the correct !flow->qentry guard. Apply the same guard to the CONFIRM_LINK/ADD_LINK_CONT branch so that a duplicate message when qentry is already occupied falls through to break and is freed by the kfree(qentry) at the out: label, rather than silently leaking the existing allocation. The response direction (smc_llc_rx_response()) is unaffected: it already guards with flow->qentry at the equivalent site and drops duplicate responses correctly.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 22, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before e384f3cba6ea709f5b2272b1770db4ce14047f78; from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before a1e980d7a9e7ee6faf4f5fd7b450413b969af26d; from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before e0eb87677c76b157cdf8eb7c1f19e56227165a33; from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before 06734dfeaeba886aab1bf147249195b888ac3e4d; from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before c23c409228629107203d3c3e95fff1473173f1a6; from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before 10cb31b2b74cb664c6c95cf72364d7d5c483ab82; from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before bfc336a9fbbf09805f3dfe25c195a4db90af2846; from 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 before 976245094925bab9bc39366b2e9ab44ffcde61d0 | CNA record |
References
- https://git.kernel.org/stable/c/e384f3cba6ea709f5b2272b1770db4ce14047f78
- https://git.kernel.org/stable/c/a1e980d7a9e7ee6faf4f5fd7b450413b969af26d
- https://git.kernel.org/stable/c/e0eb87677c76b157cdf8eb7c1f19e56227165a33
- https://git.kernel.org/stable/c/06734dfeaeba886aab1bf147249195b888ac3e4d
- https://git.kernel.org/stable/c/c23c409228629107203d3c3e95fff1473173f1a6
- https://git.kernel.org/stable/c/10cb31b2b74cb664c6c95cf72364d7d5c483ab82
- https://git.kernel.org/stable/c/bfc336a9fbbf09805f3dfe25c195a4db90af2846
- https://git.kernel.org/stable/c/976245094925bab9bc39366b2e9ab44ffcde61d0
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.