Skip to content
Noroxi
CVE-2026-64010· NVD / CVE Program· CNA Linux

nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc()

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0b45c31746e1523d5d482fda8fcf54a35ac417f1, 650bdd8fdfab64a09ee474150313dbc48c374795, ad8a27d63cac96bac441edd002209ebd996e12fb.

Low priority for now. Upgrade to Linux Linux 0b45c31746e1523d5d482fda8fcf54a35ac417f1, 650bdd8fdfab64a09ee474150313dbc48c374795, ad8a27d63cac96bac441edd002209ebd996e12fb or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() A race condition exists in the NFC LLCP connection state machine where the connection acceptance packet (CC) can be processed concurrently with socket release. This can lead to a use-after-free of the socket object. When nfc_llcp_recv_cc() moves the socket from the connecting_sockets list to the sockets list, it does so without holding the socket lock. If llcp_sock_release() is executing concurrently, it might have already unlinked the socket and dropped its references, which can result in nfc_llcp_recv_cc() linking a freed socket into the live list. Fix this by holding lock_sock() during the state transition and list movement in nfc_llcp_recv_cc(). After acquiring the lock, check if the socket is still hashed to ensure it hasn't already been unlinked and marked for destruction by the release path. This aligns the locking pattern with recv_hdlc() and recv_disc().

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 13, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64010

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.6 and later · before 5.10.259
  • linux linux kernel5.11 and later · before 5.15.210
  • linux linux kernel5.16 and later · before 6.1.176
  • linux linux kernel6.2 and later · before 6.6.143
  • linux linux kernel6.7 and later · before 6.12.93
  • linux linux kernel6.13 and later · before 6.18.35
  • linux linux kernel6.19 and later · before 7.0.12
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.6affected
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before dce85215a6c7b0fd753f577a4c487f647119884caffected · git
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before bd08bb7443c501d2f2a71d529e4afcf11c9b07d2affected · git
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before 0b45c31746e1523d5d482fda8fcf54a35ac417f1affected · git
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2affected · git
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before ad8a27d63cac96bac441edd002209ebd996e12fbaffected · git
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before 650bdd8fdfab64a09ee474150313dbc48c374795affected · git
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183affected · git
    • a69f32af86e389dd232b1bb2269e202c1bfcc60f and later · before b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77affected · git
    • before 3.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.12-17.0.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64008Jul 19, 2026 · accel/rocket: fix UAF via dangling GEM handle in create_bo
    31Monitor
  • ← EarlierCVE-2026-64009Jul 19, 2026 · xfrm: Check for underflow in xfrm_state_mtu
    31Monitor
  • Later →CVE-2026-64011Jul 19, 2026 · nfc: llcp: Fix use-after-free in llcp_sock_release()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0b45c31746e1523d5d482fda8fcf54a35ac417f1Vendor (CNA)
Linux Linux650bdd8fdfab64a09ee474150313dbc48c374795Vendor (CNA)
Linux Linuxad8a27d63cac96bac441edd002209ebd996e12fbVendor (CNA)
Linux Linuxb2a60f7f846faaf5c2cdad4ea6d3a33e5f863183Vendor (CNA)
Linux Linuxb493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77Vendor (CNA)
Linux Linuxbd08bb7443c501d2f2a71d529e4afcf11c9b07d2Vendor (CNA)
Linux Linuxdce85215a6c7b0fd753f577a4c487f647119884cVendor (CNA)
Linux Linuxee2d1a8a1833c5e56e9a1745e64b0b4edda732c2Vendor (CNA)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records