CVE-2026-31660
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.253
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.169
- Linux Kernel < 6.6.135
- Linux Kernel < 6.12.82
- Linux Kernel < 6.18.23
- Linux Kernel < 6.19.13
- Linux Kernel 5.5
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31660.md and follow it. Check whether this project is affected by CVE-2026-31660. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/07cb6c72e66ba548679f22ac29ad588da8999279
- https://git.kernel.org/stable/c/16649adc2e19509104245ea1f349b629d858f11f
- https://git.kernel.org/stable/c/21ae2cda66a55c759607bbf1d23cbaa42019d2de
- https://git.kernel.org/stable/c/2ca64fb7e2d2ae14619dd204d4f2f0a601f421fb
- https://git.kernel.org/stable/c/7e37da42eda45d7859d9273fc7e225d8df458038
- https://git.kernel.org/stable/c/8b71299d587d9e4c830c18afb884c80ddb30ad28
- https://git.kernel.org/stable/c/a9495069b43b8634c1ae0042e888766c34f66637
- https://git.kernel.org/stable/c/c71ba669b570c7b3f86ec875be222ea11dacb352
References
- https://git.kernel.org/stable/c/07cb6c72e66ba548679f22ac29ad588da8999279
- https://git.kernel.org/stable/c/16649adc2e19509104245ea1f349b629d858f11f
- https://git.kernel.org/stable/c/21ae2cda66a55c759607bbf1d23cbaa42019d2de
- https://git.kernel.org/stable/c/2ca64fb7e2d2ae14619dd204d4f2f0a601f421fb
- https://git.kernel.org/stable/c/7e37da42eda45d7859d9273fc7e225d8df458038
- https://git.kernel.org/stable/c/8b71299d587d9e4c830c18afb884c80ddb30ad28
- https://git.kernel.org/stable/c/a9495069b43b8634c1ae0042e888766c34f66637
- https://git.kernel.org/stable/c/c71ba669b570c7b3f86ec875be222ea11dacb352