Answer in brief
CVE-2026-64010 records a Unknown severity vulnerability in nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64010 records a Unknown severity vulnerability in nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <dce85215a6c7b0fd753f577a4c487f647119884c || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <bd08bb7443c501d2f2a71d529e4afcf11c9b07d2 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <0b45c31746e1523d5d482fda8fcf54a35ac417f1 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <ad8a27d63cac96bac441edd002209ebd996e12fb || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <650bdd8fdfab64a09ee474150313dbc48c374795 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77 | dce85215a6c7b0fd753f577a4c487f647119884c, bd08bb7443c501d2f2a71d529e4afcf11c9b07d2, 0b45c31746e1523d5d482fda8fcf54a35ac417f1, ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2, ad8a27d63cac96bac441edd002209ebd996e12fb, 650bdd8fdfab64a09ee474150313dbc48c374795, b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183, b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77 |
| Linux/Linuxgeneric | 3.6 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <dce85215a6c7b0fd753f577a4c487f647119884c || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <bd08bb7443c501d2f2a71d529e4afcf11c9b07d2 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <0b45c31746e1523d5d482fda8fcf54a35ac417f1 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <ad8a27d63cac96bac441edd002209ebd996e12fb || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <650bdd8fdfab64a09ee474150313dbc48c374795 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183 || >=a69f32af86e389dd232b1bb2269e202c1bfcc60f <b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77 | dce85215a6c7b0fd753f577a4c487f647119884c, bd08bb7443c501d2f2a71d529e4afcf11c9b07d2, 0b45c31746e1523d5d482fda8fcf54a35ac417f1, ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2, ad8a27d63cac96bac441edd002209ebd996e12fb, 650bdd8fdfab64a09ee474150313dbc48c374795, b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183, b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77 |
| Linux/Linuxgeneric | 3.6 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.