Kernel crash via unbounded UART receive buffer
Published May 1, 2026 · Updated May 1, 2026
Out-of-bounds write in the Linux Kernel PN533 UART driver allows local users to crash the system through malformed UART input. pn532_receive_buf() appends each byte to dev->recv_skb but clears the partial frame only after a valid header, so headerless traffic exhausts tailroom before skb_put_u8() writes another byte. Exploitation requires local access to supply UART traffic to an active PN533-compatible NFC device; the documented impact is a kernel crash without confidentiality or integrity loss.
Summary
What happened
Out-of-bounds write in the Linux Kernel PN533 UART driver allows local users to crash the system through malformed UART input. pn532_receive_buf() appends each byte to dev->recv_skb but clears the partial frame only after a valid header, so headerless traffic exhausts tailroom before skb_put_u8() writes another byte. Exploitation requires local access to supply UART traffic to an active PN533-compatible NFC device; the documented impact is a kernel crash without confidentiality or integrity loss.
The record
- CVE
- CVE-2026-43032
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.5
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <23e925183db26cd322597679669ad29d70ed2ada
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <2c1fadd221b21d8038acfe6a0f56291881d5ff76
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <30fe3f5f6494f827d812ff179f295a8e532709d6
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <3adca9be14bf36b927193f05f5aea35a1a90e913
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <8bedf1dd5640ac8997bff00bbefe241b438df397
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <ad2f60de5045bfb5d20ea468a97c8760c6a3a4f8
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <cf2ff10183204349edfd6b972e189375fc5f1fb0
- Affected versionversion=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <f48ab6ee654ecc350434e4566bc785773f412b7e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo