PatchSiren cyber security CVE debrief
CVE-2026-80986 Linux CVE debrief
A Linux kernel vulnerability was resolved, involving net/smc: bound the peer rkey counts in SMC-Rv2 LLC messages. The vulnerability causes a slab-out-of-bounds read due to accessing memory past the end of an allocated buffer when handling SMC-Rv2 LLC messages. This issue arises from the incorrect handling of the v2 extension in LLC messages, leading to out-of-bounds memory access. Linux kernel developers, maintainers, and users who rely on SMC-Rv2 LLC message handling in their systems should assess exposure and verify buffer allocation and bounds checking in affected Linux kernel versions.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-09-11
- Advisory updated
- 2026-09-11
Who should care
Linux kernel developers, maintainers, and users who rely on SMC-Rv2 LLC message handling in their systems should assess exposure and verify buffer allocation and bounds checking in affected Linux kernel versions. This includes those responsible for maintaining and securing Linux-based systems, as well as developers who work with SMC-Rv2 LLC message handling.
Why it matters
Linux kernel vulnerability CVE-2026-80986 causes slab-out-of-bounds read, defenders should verify SMC-Rv2 LLC message handling and buffer allocation.
- Verify SMC-Rv2 LLC message handling and buffer allocation in Linux kernel versions
- Assess exposure and potential consequences of slab-out-of-bounds read vulnerability
Technical summary
The Linux kernel vulnerability causes a slab-out-of-bounds read due to accessing memory past the end of an allocated buffer when handling SMC-Rv2 LLC messages. This issue arises from the incorrect handling of the v2 extension in LLC messages, leading to out-of-bounds memory access. The vulnerability was introduced due to the incorrect handling of the v2 extension in LLC messages. Defenders should verify SMC-Rv2 LLC message handling and buffer allocation in Linux kernel versions that may be affected by this vulnerability.
Defensive priority
Verify SMC-Rv2 LLC message handling and buffer allocation in Linux kernel versions that may be affected by this vulnerability.
Recommended defensive actions
- Review Linux kernel versions and SMC-Rv2 LLC message handling implementations for potential exposure
- Verify buffer allocation and bounds checking in affected Linux kernel versions
- Apply patches or updates provided by the Linux kernel maintainers
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The NVD entry for CVE-2026-80986 provides details on the vulnerability, including a description and references to the Linux kernel patches. The vulnerability was introduced due to the incorrect handling of the v2 extension in LLC messages, leading to out-of-bounds memory access. Defenders should verify SMC-Rv2 LLC message handling and buffer allocation in Linux kernel versions that may be affected by this vulnerability. The Linux kernel patches provide a fix for this issue, and users should apply these patches to their systems.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-80986 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-80986
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-80986 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80986
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2d1e7c5aaa3326e95e2058457f172ca99a9a4577
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/486c699a8cde82c1d9b4f443eeab4ddf86358cb0
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/5e5d9e6df677d30a2203d257b5fd8b99814fa607
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.