CVE-2026-80795

Description

A flaw was found in the Linux kernel's Near Field Communication (NFC) subsystem. This vulnerability occurs because the system does not properly check the size of a memory area before writing new data, leading to an out-of-bounds write. A local attacker or a malicious NFC device could exploit this by repeatedly triggering certain discovery and activation processes. This could result in memory corruption, potentially causing the system to crash and become unavailable (Denial of Service).

Statement

This vulnerability is classified as Moderate rather than Important because exploitation requires local access or proximity to a specialized NFC device, restricting the impact primarily to a local denial of service. Typical Red Hat Enterprise Linux environments do not configure or expose Near Field Communication interfaces, and the affected code paths are not present in standard supported enterprise kernel configurations. Consequently, standard server deployments face minimal exposure unless systems actively interact with untrusted NFC hardware.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.