CVE-2026-74719

net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()

N/A
Published: August 22, 2026 at 03:33 PM UTC
Updated: October 14, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0fb0b02bd6fd26cba38002be4a6bbcae2228fd445.8
Vendor states this is fixed in 06734dfeaeba886aab1bf147249195b888ac3e4d (fixed)
Vendor states this is fixed in 10cb31b2b74cb664c6c95cf72364d7d5c483ab82 (fixed)
Vendor states this is fixed in 976245094925bab9bc39366b2e9ab44ffcde61d0 (fixed)
Vendor states this is fixed in a1e980d7a9e7ee6faf4f5fd7b450413b969af26d (fixed)
Vendor states this is fixed in bfc336a9fbbf09805f3dfe25c195a4db90af2846 (fixed)
Vendor states this is fixed in c23c409228629107203d3c3e95fff1473173f1a6 (fixed)
Vendor states this is fixed in e0eb87677c76b157cdf8eb7c1f19e56227165a33 (fixed)
Vendor states this is fixed in e384f3cba6ea709f5b2272b1770db4ce14047f78 (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card