SECUFOCUSNOW
Home›CVE index›CVE-2026-64010
Review reviewHigh

CVE-2026-64010

Linux

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 reference...

CVSS
8.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 8.8

Vulnerability overview

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 reference...

Affected product and versions

Product
Linux
Affected versions
>= a69f32af86e389dd232b1bb2269e202c1bfcc60f < dce85215a6c7b0fd753f577a4c487f647119884c, >= a69f32af86e389dd232b1bb2269e202c1bfcc60f < bd08bb7443c501d2f2a71d529e4afcf11c9b07d2, >= a69f32af86e389dd232b1bb2269e202c1bfcc60f < 0b45c31746e1523d5d482fda8fcf54a35ac417f1, >= a69f32af86e389dd232b1bb2269e202c1bfcc60f < ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2, >= a69f32af86e389dd232b1bb2269e202c1bfcc60f < ad8a27d63cac96bac441edd002209ebd996e12fb, >= a69f32af86e389dd232b1bb2269e202c1bfcc60f < 650bdd8fdfab64a09ee474150313dbc48c374795, >= a69f32af86e389dd232b1bb2269e202c1bfcc60f < b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183, >= a69f32af86e389dd232b1bb2269e202c1bfcc60f < b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77, >= 3.6
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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