Skip to main content

Linux CVE-2026-23372

| EUVDEUVD-2026-15359 HIGH
2026-03-25 Linux
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Local shell access
  2. Delivery
    Open NFC raw socket
  3. Exploit
    Queue NFC transmission (tx_work)
  4. Install
    Send SIGKILL to own process
  5. C2
    Trigger rawsock_release race
  6. Execute
    Use-after-free in tx_work execution
  7. Impact
    Kernel memory corruption
  8. Step 8
    Privilege escalation to root

Vulnerability Assessment

Exploitation Conditions

Requires authenticated local access with sufficient privileges to create NFC raw sockets (typically requires CAP_NET_RAW capability or membership in specific device access groups like 'nfc' on some distributions). System must have NFC hardware present or NFC kernel modules loaded (nfc.ko, nci.ko). Exploitation depends on winning a narrow race condition between process termination (socket teardown) and asynchronous workqueue execution, which may require multiple attempts but is achievable with low complexity (AC:L) through process lifecycle manipulation. Attack is NOT remotely exploitable (AV:L) and does NOT work against systems with NFC subsystem disabled, modules blacklisted, or without NFC device nodes accessible to the attacker's user context. User interaction is not required (UI:N) once the attacker has local shell access.

Impact

Real-world risk is LIMITED despite the HIGH CVSS 7.8 score. CVSS vector (AV:L/AC:L/PR:L/UI:N) indicates local attack requiring authenticated low-privilege user access with low complexity, but EPSS score of 0.02% (6th percentile) suggests minimal observed exploitation activity. No CISA KEV listing confirms this is not actively exploited in the wild. The vulnerability requires local authenticated access to NFC-enabled systems and the ability to open NFC raw sockets, which typically requires specific permissions or group membership (often restricted to privileged users in practice). Attack complexity is low once access is obtained, but the attack surface is narrow - limited to systems with NFC hardware, loaded NFC kernel modules, and applications actively using raw NFC sockets. The use-after-free can achieve arbitrary code execution in kernel context (C:H/I:H/A:H), making this a complete system compromise if successfully exploited. However, Debian tracking this across 8 releases and patches available in all active stable branches (6.1 LTS through 7.0 mainline) indicate good patch coverage. Priority should be MEDIUM for NFC-enabled edge devices, IoT gateways, and mobile/embedded systems where local access models differ from traditional servers. For server infrastructure without NFC hardware or with NFC modules blacklisted, risk is NEGLIGIBLE. The 14-year code age (since kernel 3.1) without prior exploitation suggests low in-the-wild feasibility despite technical severity.

Exploit ScenarioDerived

An authenticated local attacker with low privileges on an NFC-enabled Linux system opens an NFC raw socket and initiates data transmission to queue tx_work on the system workqueue. The attacker immediately sends SIGKILL to their own process, triggering abrupt socket teardown in rawsock_release() before tx_work executes. The race condition causes tx_work to access freed socket and NFC device structures, resulting in use-after-free memory corruption. The attacker can potentially control freed memory contents through heap spraying techniques to redirect execution flow and achieve arbitrary kernel code execution with full system privileges. No public exploit code identified at time of analysis, but the race window and memory corruption primitive are well-understood exploit techniques for local privilege escalation.

This Week Schedule remediation this week. Why: Active threat signals + CRITICAL/HIGH severity.
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Apr 18, 2026

Local privilege escalation and denial of service in Linux kernel NFC rawsock implementation (versions 3.1 through 6.19.6, patched in 6.1.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7, 7.0-rc3) allows authenticated local users to trigger use-after-free conditions via race between socket teardown and asynchronous NFC data transmission. CVSS 7.8 HIGH with local attack vector requiring low privileges. EPSS score 0.02% (6th percentile) indicates minimal real-world exploitation probability. Vendor patches available across all stable kernel branches since early 2026.

Earlier versions of this analysis (1)
v1 Mar 25, 2026 - 10:45 CVSS 7.8

A race condition exists in the Linux kernel's NFC rawsock implementation where the tx_work function can execute concurrently with socket teardown, leading to use-after-free vulnerabilities when accessing NCI device structures. This affects all Linux kernel versions with the vulnerable NFC rawsock code path, particularly impacting systems where processes are forcefully terminated (e.g., via SIGKILL). An attacker with local access to trigger socket teardown race conditions could cause kernel memory corruption, information disclosure, or denial of service.

RemediationAI

Upgrade to patched Linux kernel versions: 6.1.167 or later for 6.1 LTS branch, 6.6.130+ for 6.6 stable, 6.12.77+ for 6.12 stable, 6.18.17+ for 6.18 stable, 6.19.7+ for 6.19 stable, or 7.0-rc3+ for mainline development. Distribution-specific updates should be applied through normal package management (apt/yum/dnf) as vendors backport fixes to supported kernel versions. If immediate patching is not feasible, implement these compensating controls with noted trade-offs: (1) Blacklist NFC kernel modules (nfc.ko, nci.ko) via /etc/modprobe.d/ configuration to prevent module loading - eliminates NFC functionality entirely but removes attack surface on systems not requiring NFC; (2) Restrict access to /dev/nfc* device nodes and NFC socket creation using AppArmor/SELinux policies or group-based permissions - reduces attack surface to explicitly authorized users but requires policy customization and may break legitimate NFC applications; (3) Disable NFC subsystem at boot via kernel command line parameter (nfc.disable=1 if available) - OS-level mitigation but requires bootloader reconfiguration and reboot. Workarounds reduce but do not eliminate risk as race conditions may still trigger under specific timing conditions. Patching remains the definitive remediation. Verify patch application by checking kernel version with 'uname -r' and confirming commit presence with 'git log' on kernel source or reviewing distribution security advisories.

Affected VersionsENISA

Linux 23b7869c0fd08d73c9f83a2db88a13312d6198bb <3ae592ed91bb4b6b51df256b51045c13d2656049
Linux patch: 7.0-rc3
Linux patch: 6.18.17
Linux patch: 6.6.130
Linux 23b7869c0fd08d73c9f83a2db88a13312d6198bb <78141b8832e16d80d09cbefb4258612db0777a24
Linux 23b7869c0fd08d73c9f83a2db88a13312d6198bb <da4515fc8263c5933ed605e396af91079806dc45
Linux patch: 6.19.7
Linux 3.1
Linux patch: 0
Linux 23b7869c0fd08d73c9f83a2db88a13312d6198bb <d793458c45df2aed498d7f74145eab7ee22d25aa
Linux 23b7869c0fd08d73c9f83a2db88a13312d6198bb <edc988613def90c5b558e025b1b423f48007be06
Linux patch: 6.1.167
Linux patch: 6.12.77
Linux 23b7869c0fd08d73c9f83a2db88a13312d6198bb <722a28b635ec281bb08a23885223526d8e7d6526

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability exists in the Linux kernel's NFC (Near Field Communication) rawsock implementation, specifically in the socket release path. The rawsock_release() function failed to properly synchronize with the asynchronous tx_work workqueue task before tearing down socket and device structures. The tx_work handler (rawsock_tx_work) executes on the system workqueue and calls nfc_data_exchange(), which dereferences NCI (NFC Controller Interface) device structures. When a process using an NFC raw socket is terminated abruptly (e.g., via SIGKILL), a race condition occurs: the socket and underlying NFC device may be freed while tx_work is still queued or executing, leading to use-after-free memory corruption. The affected code path has existed since Linux kernel 3.1 when the NFC rawsock functionality (commit 23b7869c0fd0) was introduced. The vulnerability represents a classic asynchronous resource management failure where concurrent execution paths access shared resources without proper lifetime management and synchronization primitives.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SUSE 5.2 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Analysis Updated
Apr 18, 2026 - 09:34 vuln.today
v2 - CVSS changed
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
CVE Published
Mar 25, 2026 - 10:27 nvd
HIGH 7.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

nfc: rawsock: cancel tx_work before socket teardown

In rawsock_release(), cancel any pending tx_work and purge the write queue before orphaning the socket. rawsock_tx_work runs on the system workqueue and calls nfc_data_exchange which dereferences the NCI device. Without synchronization, tx_work can race with socket and device teardown when a process is killed (e.g. by SIGKILL), leading to use-after-free or leaked references.

Set SEND_SHUTDOWN first so that if tx_work is already running it will see the flag and skip transmitting, then use cancel_work_sync to wait for any in-progress execution to finish, and finally purge any remaining queued skbs.

Executive ViewAI

Why It Matters

CVE-2026-23372 is a local privilege escalation vulnerability in the Linux kernel NFC subsystem affecting versions 3.1 through 6.19.6 that allows authenticated users to crash systems or gain elevated privileges through a race condition. Organizations running affected kernel versions on systems where local user access is possible should prioritize kernel updates to prevent unauthorized privilege escalation and service disruption.

Business Impact: Medium
Compensating Controls

Apply vendor patch. Interim mitigation: restrict local user access via SSH and physical console policies; disable NFC kernel modules if unused (echo blacklist nfc > /etc/modprobe.d/disable-nfc.conf).

Threat Intelligence Overview

EPSS Score
0.0%
Top 94% exploitable
Threat Intel
1
1 source
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat Yes
Deciding rule
Active threat signals + CRITICAL/HIGH severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: +10
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in Linux Kernel Multiple Vulnerabilities

View all 4

Vendor StatusVendor

Debian

linux
Release Status Fixed Version Urgency
bullseye vulnerable 5.10.223-1 -
bullseye (security) vulnerable 5.10.251-1 -
bookworm vulnerable 6.1.159-1 -
bookworm (security) vulnerable 6.1.164-1 -
trixie vulnerable 6.12.73-1 -
trixie (security) vulnerable 6.12.74-2 -
forky, sid fixed 6.19.8-1 -
(unstable) fixed 6.19.8-1 -

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Threat IntelligenceMISP

CISA Advisories
Sources: CISA (public domain)

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy