CVE-2026-43098
What it is
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.
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
- Modified
Affected
- Linux Kernel < 6.6.136
- Linux Kernel < 6.12.83
- Linux Kernel < 6.18.24
- Linux Kernel < 6.19.14
- Linux Kernel 7.0
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-43098.md and follow it. Check whether this project is affected by CVE-2026-43098. 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/09822d3d6f68a0cdc4626e0c507324a4927f55a9
- https://git.kernel.org/stable/c/5c14a19d5b1645cce1cb1252833d70b23635b632
- https://git.kernel.org/stable/c/6d931680a9851481c3243689488eafed08eeff71
- https://git.kernel.org/stable/c/7c31f7a599cf00fad3c204092a91a924126c67e4
- https://git.kernel.org/stable/c/d8c2aa3c4a1ec530a485e46a1c4f1a118bb00156
References
- https://git.kernel.org/stable/c/09822d3d6f68a0cdc4626e0c507324a4927f55a9
- https://git.kernel.org/stable/c/20a57de2e79b797ed75382659d52bf4c7d9cb446
- https://git.kernel.org/stable/c/5c14a19d5b1645cce1cb1252833d70b23635b632
- https://git.kernel.org/stable/c/6d931680a9851481c3243689488eafed08eeff71
- https://git.kernel.org/stable/c/7c31f7a599cf00fad3c204092a91a924126c67e4
- https://git.kernel.org/stable/c/d8c2aa3c4a1ec530a485e46a1c4f1a118bb00156
- https://git.kernel.org/stable/c/e4ab0fd1c91882f2a7846b1817781c8741f7f315