Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-31660

5.5 · MEDIUM

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.

Published Apr 24, 2026EPSS 0.16%

Overview

CVE-2026-31660 is a medium-severity vulnerability. It was published on April 24, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/07cb6c72e66ba548679f22ac29ad588da8999279Refgit.kernel.org/stable/c/16649adc2e19509104245ea1f349b629d858f11fRefgit.kernel.org/stable/c/21ae2cda66a55c759607bbf1d23cbaa42019d2deRefgit.kernel.org/stable/c/2ca64fb7e2d2ae14619dd204d4f2f0a601f421fbRefgit.kernel.org/stable/c/7e37da42eda45d7859d9273fc7e225d8df458038Refgit.kernel.org/stable/c/8b71299d587d9e4c830c18afb884c80ddb30ad28Refgit.kernel.org/stable/c/a9495069b43b8634c1ae0042e888766c34f66637Refgit.kernel.org/stable/c/c71ba669b570c7b3f86ec875be222ea11dacb352

How CyberStrike helps

Frequently asked questions

What is CVE-2026-31660?

CVE-2026-31660 is a medium-severity vulnerability. It was published on April 24, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2026-31660?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31660?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31660?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31660 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999