Memory exhaustion via duplicate SMC link requests
Published Aug 22, 2026 · Updated Aug 22, 2026
Memory leak in the Linux kernel's SMC code allows remote attackers on an adjacent network to exhaust memory via duplicate link requests. The CONFIRM_LINK and ADD_LINK_CONT branch of smc_llc_event_handler() overwrites flow->qentry without freeing the pending kmalloc-96 object. An active local LLC flow with a queued entry and an SMC-capable adjacent peer are required; repeated requests exhaust kernel memory and interrupt service.
Summary
What happened
Memory leak in the Linux kernel's SMC code allows remote attackers on an adjacent network to exhaust memory via duplicate link requests. The CONFIRM_LINK and ADD_LINK_CONT branch of smc_llc_event_handler() overwrites flow->qentry without freeing the pending kmalloc-96 object. An active local LLC flow with a queued entry and an SMC-capable adjacent peer are required; repeated requests exhaust kernel memory and interrupt service.
The record
- CVE
- CVE-2026-74719
- Published
- Aug 22, 2026
- Updated
- Aug 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-772, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <06734dfeaeba886aab1bf147249195b888ac3e4d
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <10cb31b2b74cb664c6c95cf72364d7d5c483ab82
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <976245094925bab9bc39366b2e9ab44ffcde61d0
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <a1e980d7a9e7ee6faf4f5fd7b450413b969af26d
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <bfc336a9fbbf09805f3dfe25c195a4db90af2846
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <c23c409228629107203d3c3e95fff1473173f1a6
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <e0eb87677c76b157cdf8eb7c1f19e56227165a33
- Affected versionversion=0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 <e384f3cba6ea709f5b2272b1770db4ce14047f78
- Affected versionversion=5.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo