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-43098nfc: s3fwrn5: allocate rx skb before consuming bytes

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: s3fwrn5: allocate rx skb before consuming bytes s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete 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. · 5 days later

    Published

  3. · 26 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-43098, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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 (16 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 3f52c2cb7e3ada37513dabb69a22cf917dba754f – < 20a57de2e79b797ed75382659d52bf4c7d9cb446
    • affected 3f52c2cb7e3ada37513dabb69a22cf917dba754f – < e4ab0fd1c91882f2a7846b1817781c8741f7f315
    • affected 3f52c2cb7e3ada37513dabb69a22cf917dba754f – < d8c2aa3c4a1ec530a485e46a1c4f1a118bb00156
    • affected 3f52c2cb7e3ada37513dabb69a22cf917dba754f – < 7c31f7a599cf00fad3c204092a91a924126c67e4
    • affected 3f52c2cb7e3ada37513dabb69a22cf917dba754f – < 6d931680a9851481c3243689488eafed08eeff71
    • affected 3f52c2cb7e3ada37513dabb69a22cf917dba754f – < 09822d3d6f68a0cdc4626e0c507324a4927f55a9
    • affected 3f52c2cb7e3ada37513dabb69a22cf917dba754f – < 5c14a19d5b1645cce1cb1252833d70b23635b632
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .