Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
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.28% (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 36c644c63bfcaee2d3a426f45e89a9cd09799318, 390d82733a953c1fabf3de9c9618091a7a9c90a6, 4.14.283.
Low priority for now. Upgrade to Linux Linux 36c644c63bfcaee2d3a426f45e89a9cd09799318, 390d82733a953c1fabf3de9c9618091a7a9c90a6, 4.14.283 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: fix dangling sco_conn and use-after-free in sco_sock_timeout Connecting the same socket twice consecutively in sco_sock_connect() could lead to a race condition where two sco_conn objects are created but only one is associated with the socket. If the socket is closed before the SCO connection is established, the timer associated with the dangling sco_conn object won't be canceled. As the sock object is being freed, the use-after-free problem happens when the timer callback function sco_sock_timeout() accesses the socket. Here's the call trace: dump_stack+0x107/0x163 ? refcount_inc+0x1c/ print_address_description.constprop.0+0x1c/0x47e ? refcount_inc+0x1c/0x7b kasan_report+0x13a/0x173 ? refcount_inc+0x1c/0x7b check_memory_region+0x132/0x139 refcount_inc+0x1c/0x7b sco_sock_timeout+0xb2/0x1ba process_one_work+0x739/0xbd1 ? cancel_delayed_work+0x13f/0x13f ? __raw_spin_lock_init+0xf0/0xf0 ? to_kthread+0x59/0x85 worker_thread+0x593/0x70e kthread+0x346/0x35a ? drain_workqueue+0x31a/0x31a ? kthread_bind+0x4b/0x4b ret_from_fork+0x1f/0x30
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 19th 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.2%
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 kernel4.4.284 and later · before 4.5
- linux linux kernel4.9.238 and later · before 4.9.318
- linux linux kernel4.14.247 and later · before 4.14.283
- linux linux kernel4.19.207 and later · before 4.19.247
- linux linux kernel5.4.146 and later · before 5.4.198
- linux linux kernel5.10.65 and later · before 5.10.121
- linux linux kernel5.13.17 and later · before 5.14
- linux linux kernel5.14.4 and later · before 5.15.46
- linux linux kernel5.16 and later · before 5.17.14
- linux linux kernel5.18 and later · before 5.18.3
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
- 98ae477ed1540d3acbbf44d88ee237ad64275158, f0c389e23e2475e5837716a629c81b7a9d90cc94, 0b9da4bde0d59c61b3675bdd80a05a726beb875a, 5.15affected
- 22c66af08230a7030bdb88accffaec3424695631 and later · before 9de3dc09e56f8deacd2bdbf4cecb71e11a312405affected · git
- 0115a66ebb44bd9127ccb58cf43ed23c795eb1f0 and later · before 7d61dbd7311ab978d8ddac1749a758de4de00374affected · git
- bc4b08383046f3282b6fa58cfcef05bd13e52b93 and later · before 390d82733a953c1fabf3de9c9618091a7a9c90a6affected · git
- 5ccb04c6e1fb7b97fa2e1785b67c3a1cb3527ef7 and later · before 6f55fac0af3531cf60d11369454c41f5fc81ab3faffected · git
- 059c2c09f4b7f97711d0d8eaa0b9877f5e7d0a75 and later · before 36c644c63bfcaee2d3a426f45e89a9cd09799318affected · git
- e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 and later · before 65d347cb39e2e6bd0c2a745ad7c928998ebb0162affected · git
- e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 and later · before 537f619dea4e3fa8ed1f8f938abffe3615794bccaffected · git
- e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 and later · before 99df16007f4bbf9abfc3478cb17d10f0d7f8906eaffected · git
- e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 and later · before 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2affected · git
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 5.18.5-1 | 5.18.5-1 |
Same product
linux: all recordsOther 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- 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 haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49472Feb 26, 2025 · net: phy: micrel: Allow probing without .driver_data22Monitor
- ← EarlierCVE-2022-49473Feb 26, 2025 · ASoC: ti: j721e-evm: Fix refcount leak in j721e_soc_probe_*22Monitor
- Later →CVE-2022-49475Feb 26, 2025 · spi: spi-fsl-qspi: check return value after calling platform_get_resource_byname()22Monitor
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 | 36c644c63bfcaee2d3a426f45e89a9cd09799318 | Vendor (CNA) |
| Linux Linux | 390d82733a953c1fabf3de9c9618091a7a9c90a6 | Vendor (CNA) |
| Linux Linux | 4.14.283 | Vendor (CNA) |
| Linux Linux | 4.19.247 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4.9.318 | Vendor (CNA) |
| Linux Linux | 5.10.121 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 5.15 | Vendor (CNA) |
| Linux Linux | 5.4.198 | Vendor (CNA) |
| Linux Linux | 537f619dea4e3fa8ed1f8f938abffe3615794bcc | Vendor (CNA) |
| Linux Linux | 65d347cb39e2e6bd0c2a745ad7c928998ebb0162 | Vendor (CNA) |
| Linux Linux | 6f55fac0af3531cf60d11369454c41f5fc81ab3f | Vendor (CNA) |
| Linux Linux | 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 | Vendor (CNA) |
| Linux Linux | 7d61dbd7311ab978d8ddac1749a758de4de00374 | Vendor (CNA) |
| Linux Linux | 99df16007f4bbf9abfc3478cb17d10f0d7f8906e | Vendor (CNA) |
| Linux Linux | 9de3dc09e56f8deacd2bdbf4cecb71e11a312405 | Vendor (CNA) |
| debian:linux | 5.18.5-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 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/390d82733a953c1fabf3de9c9618091a7a9c90a6
- git.kernel.org/stable/c/537f619dea4e3fa8ed1f8f938abffe3615794bcc
- git.kernel.org/stable/c/65d347cb39e2e6bd0c2a745ad7c928998ebb0162
- git.kernel.org/stable/c/6f55fac0af3531cf60d11369454c41f5fc81ab3f
- git.kernel.org/stable/c/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2
- git.kernel.org/stable/c/7d61dbd7311ab978d8ddac1749a758de4de00374
- git.kernel.org/stable/c/99df16007f4bbf9abfc3478cb17d10f0d7f8906e
- git.kernel.org/stable/c/9de3dc09e56f8deacd2bdbf4cecb71e11a312405
Vendor advisories and official records. Exploit/PoC links are deliberately left out.