CVE-2026-31660
Last modified
CVE-2026-31660 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.5.1, < 5.10.253 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.203 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.169 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.135 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.82 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.23 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.13 | — |
| Linux | Linux Kernel | 5.5 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31660?
How severe is CVE-2026-31660?
How do I fix CVE-2026-31660?
Are you affected by CVE-2026-31660?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
