LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46869: Bluetooth: btintel_pcie: Allocate memory for driver private data

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel_pcie: Allocate memory for driver private data Fix driver not allocating memory for struct btintel_data which is used to store internal data.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-46869 is a Linux kernel Bluetooth driver flaw where the btintel_pcie driver failed to allocate memory for its private data. The public record confirms a kernel fix, but does not describe business impact, attacker requirements, or exploitability.

Executive priority

Treat as a kernel maintenance item until vendor advisories clarify impact. Prioritize normal patch cycles, with faster handling for fleets using Linux Bluetooth hardware or affected upstream kernel branches.

Technical view

The issue is in Linux kernel Bluetooth btintel_pcie handling. The resolved change allocates memory for struct btintel_data, which stores internal driver data. Affected versions listed include Linux 6.10, 6.10.12, 6.11.1, and 6.12, with stable kernel commits referenced as fixes.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the btintel_pcie Bluetooth driver is present or used. The source bundle does not identify distributions, hardware models, configurations, or cloud exposure patterns.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source reports active exploitation. Public sources provided do not describe exploit technique, attack vector, prerequisites, or practical impact.

Researcher notes

The record lacks CVSS, CWE, impact class, and exploitability details. Analysis should stay anchored to the upstream fix: missing allocation for btintel_data in btintel_pcie. Validate exposure through kernel version, driver presence, and vendor backport mapping.

Mitigation direction

  • Review vendor kernel advisories for CVE-2024-46869 applicability.
  • Apply kernel updates containing the referenced stable commits.
  • Prioritize systems using Bluetooth hardware and affected kernel versions.
  • Track distribution backports, because fixed package versions may differ from upstream versions.

Validation and detection

  • Inventory Linux kernel versions across managed endpoints and servers.
  • Check whether btintel_pcie Bluetooth driver is present or loaded.
  • Confirm installed kernel packages include the referenced upstream fix commits.
  • Document any affected systems awaiting vendor-provided updates.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-46869 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6e65a09f927566f257322358d429b267548473eb, 6e65a09f927566f257322358d429b267548473eb, 6e65a09f927566f257322358d429b267548473ebunaffected
LinuxLinux6.10, 0, 6.10.12, 6.11.1, 6.12affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.