CVE-2026-74719

CVE CVE-2026-74719EUVD EUVD-2026-64406Published 2026-08-22T15:33:12.000Z

What the advisory describes

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.

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: 6.1.183; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <e384f3cba6ea709f5b2272b1770db4ce14047f78; 5.8; patch: 6.12.104; patch: 7.2; patch: 7.1.9; patch: 6.18.45; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <976245094925bab9bc39366b2e9ab44ffcde61d0; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <e0eb87677c76b157cdf8eb7c1f19e56227165a33; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <10cb31b2b74cb664c6c95cf72364d7d5c483ab82; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <c23c409228629107203d3c3e95fff1473173f1a6; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <a1e980d7a9e7ee6faf4f5fd7b450413b969af26d; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <bfc336a9fbbf09805f3dfe25c195a4db90af2846; patch: 5.15.216; 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <06734dfeaeba886aab1bf147249195b888ac3e4d; patch: 5.10.265; patch: 6.6.152; patch: 0

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.