Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-41063: Bluetooth: hci_core: cancel all works upon hci_unregister_dev()

Noroxi assessment

Priority: Monitor (action score 22/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.18% (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 0d151a103775dd9645c78c97f77d6e2a5298d913, 3f939bd73fed12dddc2a32a76116c19ca47c7678, 4.19.319.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0d151a103775dd9645c78c97f77d6e2a5298d913, 3f939bd73fed12dddc2a32a76116c19ca47c7678, 4.19.319 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_core: cancel all works upon hci_unregister_dev() syzbot is reporting that calling hci_release_dev() from hci_error_reset() due to hci_dev_put() from hci_error_reset() can cause deadlock at destroy_workqueue(), for hci_error_reset() is called from hdev->req_workqueue which destroy_workqueue() needs to flush. We need to make sure that hdev->{rx_work,cmd_work,tx_work} which are queued into hdev->workqueue and hdev->{power_on,error_reset} which are queued into hdev->req_workqueue are no longer running by the moment destroy_workqueue(hdev->workqueue); destroy_workqueue(hdev->req_workqueue); are called from hci_release_dev(). Call cancel_work_sync() on these work items from hci_unregister_dev() as soon as hdev->list is removed from hci_dev_list.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 29, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2024-41063

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

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

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.19.319
  • linux linux kernel4.20 and later · before 5.4.281
  • linux linux kernel5.5 and later · before 5.10.223
  • linux linux kernel5.11 and later · before 5.15.164
  • linux linux kernel5.16 and later · before 6.1.101
  • linux linux kernel6.2 and later · before 6.6.42
  • linux linux kernel6.7 and later · before 6.9.11
  • linux linux kernel6.10

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

    • dd594cdc24f2e48dab441732e6dfcafd6b0711d1, 6.8affected
    • e0b278650f07acf2e0932149183458468a731c03 and later · before 48542881997e17b49dc16b93fe910e0cfcf7a9f9affected · git
    • 98fb98fd37e42fd4ce13ff657ea64503e24b6090 and later · before 9cfc84b1d464cc024286f42a090718f9067b80edaffected · git
    • 6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2 and later · before ddeda6ca5f218b668b560d90fc31ae469adbfd92affected · git
    • da4569d450b193e39e87119fd316c0291b585d14 and later · before d2ce562a5aff1dcd0c50d9808ea825ef90da909faffected · git
    • 45085686b9559bfbe3a4f41d3d695a520668f5e1 and later · before 96600c2e5ee8213dbab5df1617293d8e847bb4faaffected · git
    • 2ab9a19d896f5a0dd386e1f001c5309bc35f433b and later · before d6cbce18370641a21dd889e8613d8153df15eb39affected · git
    • 2449007d3f73b2842c9734f45f0aadb522daf592 and later · before 3f939bd73fed12dddc2a32a76116c19ca47c7678affected · git
    • 2449007d3f73b2842c9734f45f0aadb522daf592 and later · before 0d151a103775dd9645c78c97f77d6e2a5298d913affected · git
    • 4.19.309 and later · before 4.19.319affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.106-16.1.106-1
Debian:13linuxbefore 6.9.11-16.9.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-41060Jul 29, 2024 · drm/radeon: check bo_va->bo is non-NULL before using it
    22Monitor
  • ← EarlierCVE-2024-41061Jul 29, 2024 · drm/amd/display: Fix array-index-out-of-bounds in dml2/FCLKChangeSupport
    31Monitor
  • Later →CVE-2024-41064Jul 29, 2024 · powerpc/eeh: avoid possible crash when edev->pdev changes
    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 / packageFixed versionSource
Linux Linux0d151a103775dd9645c78c97f77d6e2a5298d913Vendor (CNA)
Linux Linux3f939bd73fed12dddc2a32a76116c19ca47c7678Vendor (CNA)
Linux Linux4.19.319Vendor (CNA)
Linux Linux48542881997e17b49dc16b93fe910e0cfcf7a9f9Vendor (CNA)
Linux Linux5.10.223Vendor (CNA)
Linux Linux5.15.164Vendor (CNA)
Linux Linux5.4.281Vendor (CNA)
Linux Linux6.1.101Vendor (CNA)
Linux Linux6.6.42Vendor (CNA)
Linux Linux6.8Vendor (CNA)
Linux Linux96600c2e5ee8213dbab5df1617293d8e847bb4faVendor (CNA)
Linux Linux9cfc84b1d464cc024286f42a090718f9067b80edVendor (CNA)
Linux Linuxd2ce562a5aff1dcd0c50d9808ea825ef90da909fVendor (CNA)
Linux Linuxd6cbce18370641a21dd889e8613d8153df15eb39Vendor (CNA)
Linux Linuxddeda6ca5f218b668b560d90fc31ae469adbfd92Vendor (CNA)
debian:linux6.1.106-1 · Debian:12Package 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.

EPSS, last 120 days

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 researchers

Finders, 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.

All national notices →

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records