FKIE_CVE-2026-80986
Vulnerability from fkie_nvd - Published: 2026-09-11 20:19 - Updated: 2026-10-19 09:17| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/smc/smc_llc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "486c699a8cde82c1d9b4f443eeab4ddf86358cb0",
"status": "affected",
"version": "27ef6a9981fe74191849966a6d5e0400a4008ab8",
"versionType": "git"
},
{
"lessThan": "5e5d9e6df677d30a2203d257b5fd8b99814fa607",
"status": "affected",
"version": "27ef6a9981fe74191849966a6d5e0400a4008ab8",
"versionType": "git"
},
{
"lessThan": "2d1e7c5aaa3326e95e2058457f172ca99a9a4577",
"status": "affected",
"version": "27ef6a9981fe74191849966a6d5e0400a4008ab8",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/smc/smc_llc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.14"
},
{
"lessThan": "6.14",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: bound the peer rkey counts in SMC-Rv2 LLC messages\n\nOn a link whose device has max_recv_sge == 1 there is no shared v2 receive\nbuffer, and smc_llc_save_add_link_rkeys() takes the v2 extension from 44\nbytes past the start of the queue entry\u0027s inline message:\n\n ext = (struct smc_llc_msg_add_link_v2_ext *)(llc_msg + SMC_WR_TX_SIZE);\n\nThe entry is a 72-byte allocation and the extension starts at offset 68, so\next-\u003enum_rkeys at offset 94 is already past it. This happens on every\nSMC-Rv2 link addition, whatever the peer sends:\n\n [ 2.490065] BUG: KASAN: slab-out-of-bounds in smc_llc_save_add_link_rkeys+0x333/0x350\n [ 2.490431] Read of size 2 at addr ffff8880056406de by task smctest/106\n [ 2.490709]\n [ 2.490792] CPU: 0 UID: 0 PID: 106 Comm: smctest Not tainted 7.2.0-rc5-p1-g77a5d9d9c99f #32 PREEMPT(lazy)\n [ 2.490795] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n [ 2.490798] Call Trace:\n [ 2.490803] \u003cTASK\u003e\n [ 2.490805] dump_stack_lvl+0x53/0x70\n [ 2.490810] print_report+0xd0/0x630\n [ 2.490828] ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n [ 2.490832] ? smc_llc_save_add_link_rkeys+0x333/0x350\n [ 2.490834] kasan_report+0xce/0x100\n [ 2.490836] ? smc_llc_save_add_link_rkeys+0x333/0x350\n [ 2.490837] smc_llc_save_add_link_rkeys+0x333/0x350\n [ 2.490839] ? smcr_buf_map_lgr+0x1bf/0x2b0\n [ 2.490844] smc_llc_cli_add_link+0xca7/0x1e80\n [ 2.490848] ? smc_llc_wait+0x355/0x810\n [ 2.490850] ? __pfx_smc_llc_wait+0x10/0x10\n [ 2.490851] ? __pfx_smc_llc_cli_add_link+0x10/0x10\n [ 2.490853] ? __pfx_autoremove_wake_function+0x10/0x10\n [ 2.490863] __smc_connect+0x3f5c/0x4980\n [ 2.490873] ? __pfx_kernel_connect+0x10/0x10\n [ 2.490888] ? __pfx___smc_connect+0x10/0x10\n [ 2.490891] ? release_sock+0x148/0x1d0\n [ 2.490894] smc_connect+0x42c/0x580\n [ 2.490896] __sys_connect+0xfc/0x130\n [ 2.490898] ? __pfx___sys_connect+0x10/0x10\n [ 2.490900] ? handle_mm_fault+0x1a1/0x430\n [ 2.490908] __x64_sys_connect+0x6d/0xb0\n [ 2.490909] ? fpregs_assert_state_consistent+0x56/0xe0\n [ 2.490917] do_syscall_64+0xf9/0x540\n [ 2.490921] entry_SYSCALL_64_after_hwframe+0x77/0x7f\n [ 2.490924] RIP: 0033:0x421bb4\n [ 2.490927] Code: ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 80 3d ad 34 09 00 00 74 13 b8 2a 00 00 00 0f 05 \u003c48\u003e 3d 00 f0 ff ff 77 4c c3 0f 1f 00 55 48 89 e5 48 83 ec 10 89 55\n [ 2.490929] RSP: 002b:00007ffd473b01a8 EFLAGS: 00000202 ORIG_RAX: 000000000000002a\n [ 2.490935] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000421bb4\n [ 2.490936] RDX: 0000000000000010 RSI: 00007ffd473b01d0 RDI: 0000000000000003\n [ 2.490937] RBP: 0000000000003930 R08: 0000000000000004 R09: 0000000000000000\n [ 2.490938] R10: 00007ffd473b0f98 R11: 0000000000000202 R12: 0000000000000006\n [ 2.490939] R13: 00007ffd473b0f87 R14: 0000000000000003 R15: 00007ffd473b0f90\n [ 2.490940] \u003c/TASK\u003e\n [ 2.490941]\n [ 2.499545] Allocated by task 44:\n [ 2.499693] kasan_save_stack+0x33/0x60\n [ 2.499860] kasan_save_track+0x14/0x30\n [ 2.500026] __kasan_kmalloc+0x8f/0xa0\n [ 2.500190] __kmalloc_cache_noprof+0x158/0x370\n [ 2.500393] smc_llc_enqueue+0x72/0x560\n [ 2.500559] smc_wr_rx_tasklet_fn+0x474/0xa80\n [ 2.500747] tasklet_action_common+0x20f/0x8a0\n [ 2.500945] handle_softirqs+0x18e/0x590\n [ 2.501115] do_softirq+0x3b/0x60\n [ 2.501266] __local_bh_enable_ip+0x61/0x70\n [ 2.501446] __alloc_skb+0x732/0x890\n [ 2.501604] rxe_init_packet+0x16b/0x4f0\n [ 2.501783] prepare_ack_packet+0xb8/0x830\n [ 2.501962] rxe_receiver+0x495/0x96e0\n [ 2.502125] do_work+0x144/0x470\n [ 2.502269] process_one_work+0x633/0x1030\n [ 2.502450] worker_thread+0x45b/0xd10\n [ 2.50261\n---truncated---"
}
],
"id": "CVE-2026-80986",
"lastModified": "2026-10-19T09:17:31.197",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-09-11T20:19:05.180",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2d1e7c5aaa3326e95e2058457f172ca99a9a4577"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/486c699a8cde82c1d9b4f443eeab4ddf86358cb0"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5e5d9e6df677d30a2203d257b5fd8b99814fa607"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.