Skip to main content

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc()… (CVE-2026-98482)

0
Medium
Published: 10/18/2026 (10/18/2026, 18:31:50 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel NFC subsystem's LLCP receive handler was resolved. The function nfc_llcp_recv_hdlc() reads a sequence byte from a packet without verifying the packet length first, potentially accessing uninitialized memory. This occurs because the receive path only guarantees a two-byte LLCP header, but the sequence byte read happens before confirming the packet is long enough. The fix adds a length check to ensure the sequence byte is only read if present, dropping truncated PDUs without processing them.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/18/2026, 20:03:23 UTC

Technical Analysis

The Linux kernel NFC LLCP receive handler (nfc_llcp_recv_hdlc()) previously read the sequence byte skb->data[2] before verifying the packet length, leading to reading uninitialized memory when processing truncated I, RR, or RNR PDUs. The receive path guarantees only a two-byte LLCP header, but the sequence byte is beyond that header. The vulnerability allows a peer to influence the sequence byte read from uninitialized tailroom memory, which is not new peer control data but uninitialized memory. The patch adds a pskb_may_pull() check to ensure the sequence byte is present and linear before reading it, dropping malformed truncated PDUs without replying with a DM frame.

Potential Impact

This vulnerability results in the Linux kernel NFC LLCP handler reading uninitialized memory when processing truncated PDUs. While it does not involve new peer control data, it exposes uninitialized kernel memory contents, which may lead to information disclosure or undefined behavior. There is no indication of active exploitation in the wild.

Mitigation Recommendations

A fix has been applied in the Linux kernel to add proper length checks before reading the sequence byte in nfc_llcp_recv_hdlc(). Users should update to the fixed kernel version containing commit 95674f506c63 or later. No additional mitigation is required as the vulnerability is addressed by this official fix.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-8vvq-jjhc-wfc4
Osv Schema Version
1.4.0
Aliases
["CVE-2026-98482"]

Threat ID: 6ad520b12cdf04f656993b16

Added to database: 10/18/2026, 19:40:33 UTC

Last enriched: 10/18/2026, 20:03:23 UTC

Last updated: 10/18/2026, 22:02:57 UTC

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses