CVE-2026-46111: Bluetooth: hci_conn: fix potential UAF in create_big_sync
Noroxi assessment
Priority: Monitor (action score 31/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.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0beddb0c380bed5f5b8e61ddbe14635bb73d0b41, 1750a2df0eab61dc421a7afae74abdd239a44b85, 6823f730bf195fc296d9edd09e2ca94bc1ff5584; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0beddb0c380bed5f5b8e61ddbe14635bb73d0b41, 1750a2df0eab61dc421a7afae74abdd239a44b85, 6823f730bf195fc296d9edd09e2ca94bc1ff5584; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 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: Bluetooth: hci_conn: fix potential UAF in create_big_sync Add hci_conn_valid() check in create_big_sync() to detect stale connections before proceeding with BIG creation. Handle the resulting -ECANCELED in create_big_complete() and re-validate the connection under hci_dev_lock() before dereferencing, matching the pattern used by create_le_conn_complete() and create_pa_complete(). Keep the hci_conn object alive across the async boundary by taking a reference via hci_conn_get() when queueing create_big_sync(), and dropping it in the completion callback. The refcount and the lock are complementary: the refcount keeps the object allocated, while hci_dev_lock() serializes hci_conn_hash_del()'s list_del_rcu() on hdev->conn_hash, as required by hci_conn_del(). hci_conn_put() is called outside hci_dev_unlock() so the final put (which resolves to kfree() via bt_link_release) does not run under hdev->lock, though the release path would be safe either way. Without this, create_big_complete() would unconditionally dereference the conn pointer on error, causing a use-after-free via hci_connect_cfm() and hci_conn_del().
- Published
- May 28, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.0 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.90
- linux linux kernel6.13 and later · before 6.18.32
- linux linux kernel6.19 and later · before 7.0.7
- 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
- 6.0affected
- eca0ae4aea66914515e5e3098ea051b518ee5316 and later · before d41093723e47255d7d74df86e2736711c1b8486eaffected · git
- eca0ae4aea66914515e5e3098ea051b518ee5316 and later · before 6823f730bf195fc296d9edd09e2ca94bc1ff5584affected · git
- eca0ae4aea66914515e5e3098ea051b518ee5316 and later · before 1750a2df0eab61dc421a7afae74abdd239a44b85affected · git
- eca0ae4aea66914515e5e3098ea051b518ee5316 and later · before dc34f8d8240f25dd137dc2758ebbcc75e3779142affected · git
- eca0ae4aea66914515e5e3098ea051b518ee5316 and later · before f8eaf92c57ad99358dd372580d5ff87623343a72affected · git
- eca0ae4aea66914515e5e3098ea051b518ee5316 and later · before 0beddb0c380bed5f5b8e61ddbe14635bb73d0b41affected · git
- before 6.0not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
- 6.6.140 and later · up to and including 6.6.*not 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.187-1 | 6.1.187-1 |
| Debian:13 | linux | before 6.12.90-1 | 6.12.90-1 |
| Debian:14 | linux | before 7.0.7-1 | 7.0.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46107May 28, 2026 · dm-thin: fix metadata refcount underflow31Monitor
- ← EarlierCVE-2026-46110May 28, 2026 · net: stmmac: Prevent NULL deref when RX memory exhausted30Monitor
- Later →CVE-2026-46113May 28, 2026 · KVM: x86: Fix shadow paging use-after-free due to unexpected GFN35Monitor
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 | 0beddb0c380bed5f5b8e61ddbe14635bb73d0b41 | Vendor (CNA) |
| Linux Linux | 1750a2df0eab61dc421a7afae74abdd239a44b85 | Vendor (CNA) |
| Linux Linux | 6823f730bf195fc296d9edd09e2ca94bc1ff5584 | Vendor (CNA) |
| Linux Linux | d41093723e47255d7d74df86e2736711c1b8486e | Vendor (CNA) |
| Linux Linux | dc34f8d8240f25dd137dc2758ebbcc75e3779142 | Vendor (CNA) |
| Linux Linux | f8eaf92c57ad99358dd372580d5ff87623343a72 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-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.
No history yet (it accumulates with the daily EPSS job).
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1750a2df0eab61dc421a7afae74abdd239a44b85
- git.kernel.org/stable/c/6823f730bf195fc296d9edd09e2ca94bc1ff5584
- git.kernel.org/stable/c/d41093723e47255d7d74df86e2736711c1b8486e
- git.kernel.org/stable/c/dc34f8d8240f25dd137dc2758ebbcc75e3779142
- git.kernel.org/stable/c/f8eaf92c57ad99358dd372580d5ff87623343a72
Vendor advisories and official records. Exploit/PoC links are deliberately left out.