Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50255: Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs

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.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 1e67d8641813f1876a42eeb4f532487b8a7fb0a8, 1f1764466c33a4466363b821a25cd65c46a5a793, 48d7c24b7ef6417c68f206566364db1f8087bb23; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 1e67d8641813f1876a42eeb4f532487b8a7fb0a8, 1f1764466c33a4466363b821a25cd65c46a5a793, 48d7c24b7ef6417c68f206566364db1f8087bb23; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-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: fix null-ptr-deref in hci_read_supported_codecs Fix __hci_cmd_sync_sk() to return not NULL for unknown opcodes. __hci_cmd_sync_sk() returns NULL if a command returns a status event. However, it also returns NULL where an opcode doesn't exist in the hci_cc table because hci_cmd_complete_evt() assumes status = skb->data[0] for unknown opcodes. This leads to null-ptr-deref in cmd_sync for HCI_OP_READ_LOCAL_CODECS as there is no hci_cc for HCI_OP_READ_LOCAL_CODECS, which always assumes status = skb->data[0]. KASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077] CPU: 1 PID: 2000 Comm: kworker/u9:5 Not tainted 6.9.0-ga6bcb805883c-dirty #10 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: hci7 hci_power_on RIP: 0010:hci_read_supported_codecs+0xb9/0x870 net/bluetooth/hci_codec.c:138 Code: 08 48 89 ef e8 b8 c1 8f fd 48 8b 75 00 e9 96 00 00 00 49 89 c6 48 ba 00 00 00 00 00 fc ff df 4c 8d 60 70 4c 89 e3 48 c1 eb 03 <0f> b6 04 13 84 c0 0f 85 82 06 00 00 41 83 3c 24 02 77 0a e8 bf 78 RSP: 0018:ffff888120bafac8 EFLAGS: 00010212 RAX: 0000000000000000 RBX: 000000000000000e RCX: ffff8881173f0040 RDX: dffffc0000000000 RSI: ffffffffa58496c0 RDI: ffff88810b9ad1e4 RBP: ffff88810b9ac000 R08: ffffffffa77882a7 R09: 1ffffffff4ef1054 R10: dffffc0000000000 R11: fffffbfff4ef1055 R12: 0000000000000070 R13: 0000000000000000 R14: 0000000000000000 R15: ffff88810b9ac000 FS: 0000000000000000(0000) GS:ffff8881f6c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f6ddaa3439e CR3: 0000000139764003 CR4: 0000000000770ef0 PKRU: 55555554 Call Trace: <TASK> hci_read_local_codecs_sync net/bluetooth/hci_sync.c:4546 [inline] hci_init_stage_sync net/bluetooth/hci_sync.c:3441 [inline] hci_init4_sync net/bluetooth/hci_sync.c:4706 [inline] hci_init_sync net/bluetooth/hci_sync.c:4742 [inline] hci_dev_init_sync net/bluetooth/hci_sync.c:4912 [inline] hci_dev_open_sync+0x19a9/0x2d30 net/bluetooth/hci_sync.c:4994 hci_dev_do_open net/bluetooth/hci_core.c:483 [inline] hci_power_on+0x11e/0x560 net/bluetooth/hci_core.c:1015 process_one_work kernel/workqueue.c:3267 [inline] process_scheduled_works+0x8ef/0x14f0 kernel/workqueue.c:3348 worker_thread+0x91f/0xe50 kernel/workqueue.c:3429 kthread+0x2cb/0x360 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Nov 9, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 12th 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.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-50255

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 kernel5.17 and later · before 6.1.116
  • linux linux kernel6.2 and later · before 6.6.60
  • linux linux kernel6.7 and later · before 6.11.7
  • linux linux kernel6.12

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

    • 5.17affected
    • abfeea476c68afea54c9c050a2d3b19d5d2ee873 and later · before 5d9054b9f769a8e124c4fa02072437c864726bafaffected · git
    • abfeea476c68afea54c9c050a2d3b19d5d2ee873 and later · before 1f1764466c33a4466363b821a25cd65c46a5a793affected · git
    • abfeea476c68afea54c9c050a2d3b19d5d2ee873 and later · before 48d7c24b7ef6417c68f206566364db1f8087bb23affected · git
    • abfeea476c68afea54c9c050a2d3b19d5d2ee873 and later · before 1e67d8641813f1876a42eeb4f532487b8a7fb0a8affected · git
    • before 5.17not affected · semver
    • 6.1.116 and later · up to and including 6.1.*not affected · semver
    • 6.6.60 and later · up to and including 6.6.*not affected · semver
    • 6.11.7 and later · up to and including 6.11.*not affected · semver
    • 6.12 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
AlmaLinux:9bpftoolbefore 7.4.0-503.19.1.el9_57.4.0-503.19.1.el9_5
AlmaLinux:9kernelbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64kbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debugbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-develbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-cross-headersbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debugbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-corebefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-develbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-503.19.1.el9_55.14.0-503.19.1.el9_5

+96

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-50253Nov 9, 2024 · bpf: Check the validity of nr_words in bpf_iter_bits_new()
    22Monitor
  • ← EarlierCVE-2024-50254Nov 9, 2024 · bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
    22Monitor
  • Later →CVE-2024-50256Nov 9, 2024 · netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6()
    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 Linux1e67d8641813f1876a42eeb4f532487b8a7fb0a8Vendor (CNA)
Linux Linux1f1764466c33a4466363b821a25cd65c46a5a793Vendor (CNA)
Linux Linux48d7c24b7ef6417c68f206566364db1f8087bb23Vendor (CNA)
Linux Linux5d9054b9f769a8e124c4fa02072437c864726bafVendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.4.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-503.19.1.el9_5 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.119-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.4.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-503.19.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+1

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

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-476 · NULL Pointer Dereference

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (4 more)

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

All records