Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-42137: Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.23% (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 215a26c2404fa34625c725d446967fa328a703eb, 4ca6013cd18e58ac1044908c40d4006a92093a11, 5.10.222.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 215a26c2404fa34625c725d446967fa328a703eb, 4ca6013cd18e58ac1044908c40d4006a92093a11, 5.10.222 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: qca: Fix BT enable failure again for QCA6390 after warm reboot Commit 272970be3dab ("Bluetooth: hci_qca: Fix driver shutdown on closed serdev") will cause below regression issue: BT can't be enabled after below steps: cold boot -> enable BT -> disable BT -> warm reboot -> BT enable failure if property enable-gpios is not configured within DT|ACPI for QCA6390. The commit is to fix a use-after-free issue within qca_serdev_shutdown() by adding condition to avoid the serdev is flushed or wrote after closed but also introduces this regression issue regarding above steps since the VSC is not sent to reset controller during warm reboot. Fixed by sending the VSC to reset controller within qca_serdev_shutdown() once BT was ever enabled, and the use-after-free issue is also fixed by this change since the serdev is still opened before it is flushed or wrote. Verified by the reported machine Dell XPS 13 9310 laptop over below two kernel commits: commit e00fc2700a3f ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of bluetooth-next tree. commit b23d98d46d28 ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of linus mainline tree.

Published
Jul 30, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile
CWE
—

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.2%

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-42137

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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.2affected
    • e84ec6e25df9bb0968599e92eacedaf3a0a5b587 and later · before 215a26c2404fa34625c725d446967fa328a703ebaffected · git
    • 908d1742b6e694e84ead5c62e4b7c1bfbb8b46a3 and later · before 4ca6013cd18e58ac1044908c40d4006a92093a11affected · git
    • ea3ebda47dd56f6e1c62f2e0e1b6e1b0a973e447 and later · before e6e200b264271f62a3fadb51ada9423015ece37baffected · git
    • 272970be3dabd24cbe50e393ffee8f04aec3b9a8 and later · before e2d8aa4c763593704ac21e7591aed4f13e32f3b5affected · git
    • 272970be3dabd24cbe50e393ffee8f04aec3b9a8 and later · before 977b9dc65e14fb80de4763d949c7dec2ecb15b9baffected · git
    • 272970be3dabd24cbe50e393ffee8f04aec3b9a8 and later · before 88e72239ead9814b886db54fc4ee39ef3c2b8f26affected · git
    • 5.10.165 and later · before 5.10.222affected · semver
    • 5.15.90 and later · before 5.15.163affected · semver
    • 6.1.8 and later · before 6.1.98affected · semver
Affected versions · NVD (6)

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

  • linux linux kernel5.10.165 and later · before 5.10.222
  • linux linux kernel5.15.90 and later · before 5.15.163
  • linux linux kernel6.1.8 and later · before 6.1.98
  • linux linux kernel6.2 and later · before 6.6.39
  • linux linux kernel6.7 and later · before 6.9.9
  • linux linux kernel6.10

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.98-16.1.98-1
Debian:13linuxbefore 6.9.9-16.9.9-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-42135Jul 30, 2024 · vhost_task: Handle SIGKILL by flushing work and exiting
    22Monitor
  • ← EarlierCVE-2024-42136Jul 30, 2024 · cdrom: rearrange last_media_change check to avoid unintentional overflow
    31Monitor
  • Later →CVE-2024-42138Jul 30, 2024 · mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file
    31Monitor

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 Linux215a26c2404fa34625c725d446967fa328a703ebVendor (CNA)
Linux Linux4ca6013cd18e58ac1044908c40d4006a92093a11Vendor (CNA)
Linux Linux5.10.222Vendor (CNA)
Linux Linux5.15.163Vendor (CNA)
Linux Linux6.1.98Vendor (CNA)
Linux Linux88e72239ead9814b886db54fc4ee39ef3c2b8f26Vendor (CNA)
Linux Linux977b9dc65e14fb80de4763d949c7dec2ecb15b9bVendor (CNA)
Linux Linuxe2d8aa4c763593704ac21e7591aed4f13e32f3b5Vendor (CNA)
Linux Linuxe6e200b264271f62a3fadb51ada9423015ece37bVendor (CNA)
debian:linux6.1.98-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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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)

—

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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (6 more)

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

All records