CVE-2026-80799
Vulnerability Scoring
Analysis In Progress
CVE-2026-80799 Vulnerability Analysis & Exploit Details
CVE-2026-80799
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2026-80799 Details
Status: Received on 04 Sep 2026, 16:18 UTC
Published on: 04 Sep 2026, 16:18 UTC
CVSS Release:
CVE-2026-80799 Vulnerability Summary
CVE-2026-80799: In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() contain three related bugs in their TLV parsing loops: 1. 'offset' is declared u8 but tlv_array_len is u16. When TLV data advances offset past 255 it silently wraps to zero, causing infinite loops or double-processing of buffer data. 2. Before reading tlv[0] (type) and tlv[1] (length) there is no check that offset+2 <= tlv_array_len. A truncated TLV causes an OOB read of one byte past the buffer end. 3. After reading the length field, the value bytes are accessed without checking offset+2+length <= tlv_array_len. A crafted length=0xFF on a short buffer causes up to 255 bytes of OOB read past the buffer end. Both functions are reachable without authentication via nfc_llcp_set_remote_gb() which feeds remote LLCP general bytes directly into nfc_llcp_parse_gb_tlv() with no additional validation. Fix all three issues by widening offset from u8 to u16 and adding bounds checks for both the TLV header and value field before each access.
Assessing the Risk of CVE-2026-80799
Access Complexity Graph
The exploitability of CVE-2026-80799 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2026-80799
No exploitability data is available for CVE-2026-80799.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2026-80799, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2026-80799, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2026-80799 does not compromise confidentiality.
-
Integrity:
None
CVE-2026-80799 does not impact data integrity.
-
Availability:
None
CVE-2026-80799 does not affect system availability.
CVE-2026-80799 References
External References
- https://git.kernel.org/stable/c/2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1
- https://git.kernel.org/stable/c/2d239590d1845a706304833d40dd6d4fec20ad88
- https://git.kernel.org/stable/c/382eaa770335acf4f16a5a55524500f2bb4207df
- https://git.kernel.org/stable/c/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911
- https://git.kernel.org/stable/c/7f6f3d087c67a4346189ef2c36481455bbc59a74
- https://git.kernel.org/stable/c/875285a165fd3b402de2ab3be0deb355d6f4caf5
- https://git.kernel.org/stable/c/9c47d667963542c3cf8e3007b7f10c0904d08238
- https://git.kernel.org/stable/c/a209334ed929941b20810c17c3a507445b0a7c85
- https://git.kernel.org/stable/c/e84cdfdc4a6c88e8b751144458f2e04e24415a28
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2026-80799: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2026-87919 – The Product XML Feed Manager for WooCommerce WordPress plugin before 3.1.1 does not restrict which object method its product shortcode may call, n...
- CVE-2026-87918 – The WPBot WordPress plugin before 8.5.7 does not perform any authorization or nonce check on several AJAX actions that relay prompts to its config...
- CVE-2026-87916 – The WPBot WordPress plugin before 8.6.0 does not perform any capability or nonce check on the AJAX action that lists stored chat sessions, allowin...
- CVE-2026-87894 – The Rox Appointment Booking WordPress plugin before 1.2.3 does not perform any authorization check on the endpoint that returns a booking's confir...
- CVE-2026-87892 – The Rox Appointment Booking WordPress plugin before 1.2.0 does not verify the order total or the selected payment method against its own server-si...