CVE-2022-49754: Bluetooth: Fix a buffer overflow in mgmt_mesh_add()
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: Fix a buffer overflow in mgmt_mesh_add()
Smatch Warning:
net/bluetooth/mgmt_util.c:375 mgmt_mesh_add() error: __memcpy()
'mesh_tx->param' too small (48 vs 50)
Analysis:
'mesh_tx->param' is array of size 48. This is the destination.
u8 param[sizeof(struct mgmt_cp_mesh_send) + 29]; // 19 + 29 = 48.
But in the caller 'mesh_send' we reject only when len > 50.
len > (MGMT_MESH_SEND_SIZE + 31) // 19 + 31 = 50.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49754 is a Linux kernel Bluetooth flaw where a small buffer can be overfilled during mesh management handling. The CVSS rating is high because successful local exploitation could affect confidentiality, integrity, and availability. Evidence provided does not show internet-wide or active exploitation.
Executive priority
Treat this as a high-priority kernel maintenance issue for Linux fleets, especially shared or user-accessible systems. It does not currently have supplied evidence of active exploitation, but kernel memory corruption with high CIA impact warrants timely patch validation.
Technical view
The flaw is in net/bluetooth/mgmt_util.c mgmt_mesh_add(). A caller allows input lengths up to 50 bytes, while the destination mesh_tx->param buffer is 48 bytes. This creates a CWE-120 buffer overflow in affected Linux kernel Bluetooth code. CVSS indicates local attack vector, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions or vendor kernels carrying the vulnerable Bluetooth management code. The provided CVSS vector indicates local, low-privilege access is required. Systems without the affected kernel code path or already carrying the stable fixes are less likely exposed.
Exploitation context
The source bundle marks KEV as false, and no supplied source states active exploitation. The vulnerability is not described as remotely exploitable; CVSS lists local access with low privileges. Practical exploitability depends on kernel build, Bluetooth support, and vendor backport status.
Researcher notes
The key technical evidence is the size mismatch: 48-byte destination versus an accepted 50-byte length in the Bluetooth mesh send path. The source bundle identifies stable Linux fixes but does not provide exploit proof, distribution-specific package names, or full affected-version ranges beyond the listed kernel data.
Mitigation direction
Update to a Linux kernel or vendor package containing the referenced stable fixes.
Check distribution advisories for backported fixes, since vendor kernel versions may differ.
Prioritize patching shared, multi-user, and Bluetooth-capable Linux hosts.
Limit local user access on affected systems until remediation is confirmed.
Track vendor guidance for any Bluetooth-specific compensating controls.
Validation and detection
Inventory Linux kernel versions across servers, workstations, appliances, and embedded systems.
Identify systems with Bluetooth kernel support enabled or relevant modules present.
Compare installed kernels against vendor advisories and the referenced stable commits.
Confirm the fixed package is installed after patching and reboot into the fixed kernel.
Document exceptions where vendor status is unavailable or evidence is incomplete.
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.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.