Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31660nfc: pn533: allocate rx skb before consuming bytes

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.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 17 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31660, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 98% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 2ca64fb7e2d2ae14619dd204d4f2f0a601f421fb
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 8b71299d587d9e4c830c18afb884c80ddb30ad28
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 16649adc2e19509104245ea1f349b629d858f11f
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 07cb6c72e66ba548679f22ac29ad588da8999279
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < a9495069b43b8634c1ae0042e888766c34f66637
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 21ae2cda66a55c759607bbf1d23cbaa42019d2de
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 7e37da42eda45d7859d9273fc7e225d8df458038
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < c71ba669b570c7b3f86ec875be222ea11dacb352
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.169 – ≤ 6.1.*
    • unaffected 6.6.135 – ≤ 6.6.*
    • unaffected 6.12.82 – ≤ 6.12.*
    • unaffected 6.18.23 – ≤ 6.18.*
    • unaffected 6.19.13 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31660 badge
[![CVE-2026-31660](https://cveledger.app/badge/CVE-2026-31660.svg)](https://cveledger.app/cve/CVE-2026-31660)

Record last updated .