CVE-2026-31629

Kernel memory corruption via LLCP double release

Published Apr 24, 2026 · Updated Apr 24, 2026

Use-after-free in the Linux Kernel NFC LLCP receive path allows physically proximate attackers to corrupt kernel memory via NFC traffic. In nfc_llcp_recv_hdlc() and nfc_llcp_recv_disc(), an LLCP_CLOSED branch releases the socket but fails to return, so fall-through releases it again and underflows its reference count. Reachability requires NFC LLCP traffic while the affected socket is already closed; the published record does not establish a specific post-corruption outcome.

CVSS severity8.8
High
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in the Linux Kernel NFC LLCP receive path allows physically proximate attackers to corrupt kernel memory via NFC traffic. In nfc_llcp_recv_hdlc() and nfc_llcp_recv_disc(), an LLCP_CLOSED branch releases the socket but fails to return, so fall-through releases it again and underflows its reference count. Reachability requires NFC LLCP traffic while the affected socket is already closed; the published record does not establish a specific post-corruption outcome.

The record

CVE
CVE-2026-31629
Published
Apr 24, 2026
Updated
Apr 24, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
Unavailable
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <796e0cac058252d0ad34ebe288e6f7979b5fc9b2
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8977fad2b3c6eefd414131168d597c5d1d5e1abf
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aba4712e8f0381cd5d196534ce2ad082626a5ab6
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ff3d9e8f7244293e303f7b6ef70774291c7c27e9

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <796e0cac058252d0ad34ebe288e6f7979b5fc9b2; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8977fad2b3c6eefd414131168d597c5d1d5e1abf; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aba4712e8f0381cd5d196534ce2ad082626a5ab6; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ff3d9e8f7244293e303f7b6ef70774291c7c27e9

Published CVSS scores

8.8Linux kernel.orgCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo