CVE-2026-43032
NFC: pn533: bound the UART receive buffer
Description
In the Linux kernel, the following vulnerability has been resolved: NFC: pn533: bound the UART receive buffer pn532_receive_buf() appends every incoming byte to dev->recv_skb and only resets the buffer after pn532_uart_rx_is_frame() recognizes a complete frame. A continuous stream of bytes without a valid PN532 frame header therefore keeps growing the skb until skb_put_u8() hits the tail limit. Drop the accumulated partial frame once the fixed receive buffer is full so malformed UART traffic cannot grow the skb past PN532_UART_SKB_BUFF_LEN.
INFO
Published Date :
May 1, 2026, 3:16 p.m.
Last Modified :
May 8, 2026, 6:39 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Apply the Linux kernel patch for NFC.
- Update the Linux kernel to a fixed version.
- Configure UART receive buffer limits.
- Monitor kernel logs for buffer overflows.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-43032.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-43032 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-43032
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-43032 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-43032 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
May. 08, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.203 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.22 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.168 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.12 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.81 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.134 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.253 Added Reference Type kernel.org: https://git.kernel.org/stable/c/23e925183db26cd322597679669ad29d70ed2ada Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/2c1fadd221b21d8038acfe6a0f56291881d5ff76 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/30fe3f5f6494f827d812ff179f295a8e532709d6 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/3adca9be14bf36b927193f05f5aea35a1a90e913 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/8bedf1dd5640ac8997bff00bbefe241b438df397 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ad2f60de5045bfb5d20ea468a97c8760c6a3a4f8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/cf2ff10183204349edfd6b972e189375fc5f1fb0 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/f48ab6ee654ecc350434e4566bc785773f412b7e Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 01, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: NFC: pn533: bound the UART receive buffer pn532_receive_buf() appends every incoming byte to dev->recv_skb and only resets the buffer after pn532_uart_rx_is_frame() recognizes a complete frame. A continuous stream of bytes without a valid PN532 frame header therefore keeps growing the skb until skb_put_u8() hits the tail limit. Drop the accumulated partial frame once the fixed receive buffer is full so malformed UART traffic cannot grow the skb past PN532_UART_SKB_BUFF_LEN. Added Reference https://git.kernel.org/stable/c/23e925183db26cd322597679669ad29d70ed2ada Added Reference https://git.kernel.org/stable/c/2c1fadd221b21d8038acfe6a0f56291881d5ff76 Added Reference https://git.kernel.org/stable/c/30fe3f5f6494f827d812ff179f295a8e532709d6 Added Reference https://git.kernel.org/stable/c/3adca9be14bf36b927193f05f5aea35a1a90e913 Added Reference https://git.kernel.org/stable/c/8bedf1dd5640ac8997bff00bbefe241b438df397 Added Reference https://git.kernel.org/stable/c/ad2f60de5045bfb5d20ea468a97c8760c6a3a4f8 Added Reference https://git.kernel.org/stable/c/cf2ff10183204349edfd6b972e189375fc5f1fb0 Added Reference https://git.kernel.org/stable/c/f48ab6ee654ecc350434e4566bc785773f412b7e