Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()

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.22% (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 32df687e129ef0f9afcbcc914f7c32deb28fd481, 3945c799f12b8d1f49a3b48369ca494d981ac465, 6021ccc2471b7b95e29b7cfc7938e042bf56e281; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.

Low priority for now. Upgrade to Linux Linux 32df687e129ef0f9afcbcc914f7c32deb28fd481, 3945c799f12b8d1f49a3b48369ca494d981ac465, 6021ccc2471b7b95e29b7cfc7938e042bf56e281; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.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: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() bt_sock_alloc() attaches allocated sk object to the provided sock object. If rfcomm_dlc_alloc() fails, we release the sk object, but leave the dangling pointer in the sock object, which may cause use-after-free. Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

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
7.8
CNA · Linux
7.8
agree

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.

Follow CVE-2024-56604

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.

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 6.1.120
  • linux linux kernel6.2 and later · before 6.6.66
  • linux linux kernel6.7 and later · before 6.12.5

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

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ac3eaac4cf142a15fe67be747a682b1416efeb6eaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6021ccc2471b7b95e29b7cfc7938e042bf56e281affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 32df687e129ef0f9afcbcc914f7c32deb28fd481affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3945c799f12b8d1f49a3b48369ca494d981ac465affected · git
    • before 2.6.12not affected · semver
    • 6.1.120 and later · up to and including 6.1.*not affected · semver
    • 6.6.66 and later · up to and including 6.6.*not affected · semver
    • 6.12.5 and later · up to and including 6.12.*not affected · semver
    • 6.13 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.5-16.12.5-1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-64kbbefore 5.3.18-150300.59.188.15.3.18-150300.59.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-default-basebefore 5.3.18-150300.59.188.1.150300.18.111.15.3.18-150300.59.188.1.150300.18.111.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-docsbefore 5.3.18-150300.59.188.15.3.18-150300.59.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-obs-buildbefore 5.3.18-150300.59.188.15.3.18-150300.59.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-preemptbefore 5.3.18-150300.59.188.15.3.18-150300.59.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-sourcebefore 5.3.18-150300.59.188.15.3.18-150300.59.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-symsbefore 5.3.18-150300.59.188.15.3.18-150300.59.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.147.15.14.21-150400.24.147.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-docsbefore 5.14.21-150400.24.147.15.14.21-150400.24.147.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-obs-buildbefore 5.14.21-150400.24.147.15.14.21-150400.24.147.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-sourcebefore 5.14.21-150400.24.147.15.14.21-150400.24.147.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-symsbefore 5.14.21-150400.24.147.15.14.21-150400.24.147.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-defaultbefore 5.3.18-150300.59.188.15.3.18-150300.59.188.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-livepatch-SLE15-SP3_Update_52before 1-150300.7.3.11-150300.7.3.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_35before 1-150400.9.3.11-150400.9.3.1
SUSE:Linux Enterprise Micro 5.1kernel-rtbefore 5.3.18-150300.197.15.3.18-150300.197.1
SUSE:Linux Enterprise Micro 5.1kernel-source-rtbefore 5.3.18-150300.197.15.3.18-150300.197.1
SUSE:Linux Enterprise Micro 5.3kernel-defaultbefore 5.14.21-150400.24.147.15.14.21-150400.24.147.1
SUSE:Linux Enterprise Micro 5.3kernel-default-basebefore 5.14.21-150400.24.147.1.150400.24.72.15.14.21-150400.24.147.1.150400.24.72.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-defaultbefore 3.0.101-108.174.13.0.101-108.174.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-ec2before 3.0.101-108.174.13.0.101-108.174.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-sourcebefore 3.0.101-108.174.13.0.101-108.174.1

+5

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-56602Dec 27, 2024 · net: ieee802154: do not leave a dangling sk pointer in ieee802154_create()
    31Monitor
  • ← EarlierCVE-2024-56603Dec 27, 2024 · net: af_can: do not leave a dangling sk pointer in can_create()
    31Monitor
  • Later →CVE-2024-56605Dec 27, 2024 · Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()
    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 Linux32df687e129ef0f9afcbcc914f7c32deb28fd481Vendor (CNA)
Linux Linux3945c799f12b8d1f49a3b48369ca494d981ac465Vendor (CNA)
Linux Linux6021ccc2471b7b95e29b7cfc7938e042bf56e281Vendor (CNA)
Linux Linuxac3eaac4cf142a15fe67be747a682b1416efeb6eVendor (CNA)
azl3 kernel 6.6.64.2-9 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.76.1-1 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.3.18-150300.59.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-default3.0.101-108.174.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-default-base5.3.18-150300.59.188.1.150300.18.111.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150300.59.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-ec23.0.101-108.174.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_521-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-obs-build5.3.18-150300.59.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150300.59.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-source3.0.101-108.174.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-syms3.0.101-108.174.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-trace3.0.101-108.174.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-xen3.0.101-108.174.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage 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.

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

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 Free

CVSS vector

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

nvd-primary

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
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

  1. Fix✗ → ✓

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

References

All records