nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc()
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().
- Published
- Jul 19, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.4% · 32th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
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.
Affected systems
—
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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0b45c31746e1523d5d482fda8fcf54a35ac417f1 | Vendor (CNA) |
| Linux Linux | 650bdd8fdfab64a09ee474150313dbc48c374795 | Vendor (CNA) |
| Linux Linux | ad8a27d63cac96bac441edd002209ebd996e12fb | Vendor (CNA) |
| Linux Linux | b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183 | Vendor (CNA) |
| Linux Linux | b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77 | Vendor (CNA) |
| Linux Linux | bd08bb7443c501d2f2a71d529e4afcf11c9b07d2 | Vendor (CNA) |
| Linux Linux | dce85215a6c7b0fd753f577a4c487f647119884c | Vendor (CNA) |
| Linux Linux | ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package 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.
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 researchersFinders, 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)
—
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0b45c31746e1523d5d482fda8fcf54a35ac417f1
- git.kernel.org/stable/c/650bdd8fdfab64a09ee474150313dbc48c374795
- git.kernel.org/stable/c/ad8a27d63cac96bac441edd002209ebd996e12fb
- git.kernel.org/stable/c/b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183
- git.kernel.org/stable/c/b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77
- git.kernel.org/stable/c/bd08bb7443c501d2f2a71d529e4afcf11c9b07d2
- git.kernel.org/stable/c/dce85215a6c7b0fd753f577a4c487f647119884c
- git.kernel.org/stable/c/ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.