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-43032NFC: pn533: bound the UART receive buffer

Description

In the Linux kernel, the following vulnerability has been resolved: NFC: pn533: bound the UART receive buffer pn532_receive_buf() appends every incoming byte to dev->recv_skb and only resets the buffer after pn532_uart_rx_is_frame() recognizes a complete frame. A continuous stream of bytes without a valid PN532 frame header therefore keeps growing the skb until skb_put_u8() hits the tail limit. Drop the accumulated partial frame once the fixed receive buffer is full so malformed UART traffic cannot grow the skb past PN532_UART_SKB_BUFF_LEN.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 10 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-43032, 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.12% · top 98% of all CVEs (12 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 – < 8bedf1dd5640ac8997bff00bbefe241b438df397
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 23e925183db26cd322597679669ad29d70ed2ada
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 3adca9be14bf36b927193f05f5aea35a1a90e913
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 2c1fadd221b21d8038acfe6a0f56291881d5ff76
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < f48ab6ee654ecc350434e4566bc785773f412b7e
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < ad2f60de5045bfb5d20ea468a97c8760c6a3a4f8
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < cf2ff10183204349edfd6b972e189375fc5f1fb0
    • affected c656aa4c27b17a8c70da223ed5ab42145800d6b5 – < 30fe3f5f6494f827d812ff179f295a8e532709d6
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 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-43032 badge
[![CVE-2026-43032](https://cveledger.app/badge/CVE-2026-43032.svg)](https://cveledger.app/cve/CVE-2026-43032)

Record last updated .