Skip to main content

Linux Kernel EUVDEUVD-2026-25553

| CVE-2026-31660 MEDIUM
2026-04-24 Linux GHSA-vh7f-9w49-q39v
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

AC:H reflects that reliable exploitation requires concurrent memory allocation failure, a condition beyond attacker-controlled input alone.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

6
Analysis Generated
Jul 24, 2026 - 02:43 vuln.today
CVSS changed
Apr 27, 2026 - 20:22 NVD
5.5 (MEDIUM)
Patch released
Apr 27, 2026 - 20:17 nvd
Patch available
Patch available
Apr 24, 2026 - 16:16 EUVD
EUVD ID Assigned
Apr 24, 2026 - 15:00 euvd
EUVD-2026-25553
CVE Published
Apr 24, 2026 - 14:45 nvd
MEDIUM 5.5

DescriptionCVE.org

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

nfc: pn533: allocate rx skb before consuming bytes

pn532_receive_buf() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already hand a complete frame to pn533_recv_frame() before allocating a fresh receive buffer.

If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8().

Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.

AnalysisAI

NULL dereference in the Linux kernel's pn533 NFC driver (pn532_receive_buf) can crash the kernel when a socket buffer allocation fails after bytes have already been consumed from the serial receive stream. Systems running affected kernel versions with PN532/PN533 NFC hardware attached over serial are exposed to a local denial-of-service (kernel panic). No public exploit code exists, EPSS probability is negligible (0.02%, 7th percentile), and this vulnerability is not in the CISA KEV catalog - indicating no confirmed active exploitation.

Technical ContextAI

The vulnerability resides in the Linux kernel's NFC subsystem, specifically the pn533 driver's serdev receive-buffer callback (pn532_receive_buf). The pn533 driver supports the NXP/Philips PN532 and PN533 NFC transceiver chips commonly connected over USB-serial or UART interfaces. The serdev (serial device) framework calls receive_buf() with incoming bytes and expects the callback to return the number of accepted bytes - a strict accounting contract. The bug arises from an incorrect resource allocation order: the existing code consumes bytes into recv_skb and may dispatch a complete frame to pn533_recv_frame() before allocating a fresh receive skb via alloc_skb(). If alloc_skb() fails (e.g., under memory pressure), the function returns 0 despite having already consumed bytes, and leaves recv_skb as NULL. The subsequent receive callback then dereferences this NULL pointer in skb_put_u8(), producing a kernel NULL dereference - a class of bug closely related to CWE-476 (NULL Pointer Dereference). The fix restructures the allocation to happen lazily before consuming each byte, so that allocation failure causes an early return of the already-accepted byte count rather than a broken NULL state. CPE cpe:2.3:a:linux:linux confirms the affected product is the upstream Linux kernel.

RemediationAI

The primary fix is to upgrade the Linux kernel to a patched stable release: 5.10.253, 5.15.203, 6.1.169, 6.6.135, 6.12.82, 6.18.23, 6.19.13, or 7.0 - apply the patch corresponding to your running stable branch. Upstream fix commits are available at the kernel stable tree (https://git.kernel.org/stable/c/2ca64fb7e2d2ae14619dd204d4f2f0a601f421fb and related commits). Ubuntu users should apply the update referenced in USN-8567-1 (https://ubuntu.com/security/notices/USN-8567-1). Red Hat and SUSE users should consult their respective security portals for backported packages. If an immediate kernel update is not feasible on systems where NFC functionality is not required, unloading the pn533 and associated NFC modules (modprobe -r pn533_usb pn533 nfc) eliminates the attack surface entirely with no operational impact on non-NFC workloads; the trade-off is loss of any NFC device functionality until the module is reloaded. Blacklisting pn533 in /etc/modprobe.d/ makes this persistent across reboots.

Vendor StatusVendor

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

Share

EUVD-2026-25553 vulnerability details – vuln.today

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