CVE-2022-49111

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2022-55101 (ENISA EUVD) · GHSA-5wpf-jxv5-j2rg (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: Fix use after free in hci_send_acl

This fixes the following trace caused by receiving HCI_EV_DISCONN_PHY_LINK_COMPLETE which does call hci_conn_del without first checking if conn->type is in fact AMP_LINK and in case it is do properly cleanup upper layers with hci_disconn_cfm:

================================================================== BUG: KASAN: use-after-free in hci_send_acl+0xaba/0xc50 Read of size 8 at addr ffff88800e404818 by task bluetoothd/142

CPU: 0 PID: 142 Comm: bluetoothd Not tainted 5.17.0-rc5-00006-gda4022eeac1a #7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x45/0x59 print_address_description.constprop.0+0x1f/0x150 kasan_report.cold+0x7f/0x11b hci_send_acl+0xaba/0xc50 l2cap_do_send+0x23f/0x3d0 l2cap_chan_send+0xc06/0x2cc0 l2cap_sock_sendmsg+0x201/0x2b0 sock_sendmsg+0xdc/0x110 sock_write_iter+0x20f/0x370 do_iter_readv_writev+0x343/0x690 do_iter_write+0x132/0x640 vfs_writev+0x198/0x570 do_writev+0x202/0x280 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RSP: 002b:00007ffce8a099b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014 Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 14 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 RDX: 0000000000000001 RSI: 00007ffce8a099e0 RDI: 0000000000000015 RAX: ffffffffffffffda RBX: 00007ffce8a099e0 RCX: 00007f788fc3cf77 R10: 00007ffce8af7080 R11: 0000000000000246 R12: 000055e4ccf75580 RBP: 0000000000000015 R08: 0000000000000002 R09: 0000000000000001 R13: 000055e4ccf754a0 R14: 000055e4ccf75cd0 R15: 000055e4ccf4a6b0

Allocated by task 45: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x81/0xa0 hci_chan_create+0x9a/0x2f0 l2cap_conn_add.part.0+0x1a/0xdc0 l2cap_connect_cfm+0x236/0x1000 le_conn_complete_evt+0x15a7/0x1db0 hci_le_conn_complete_evt+0x226/0x2c0 hci_le_meta_evt+0x247/0x450 hci_event_packet+0x61b/0xe90 hci_rx_work+0x4d5/0xc50 process_one_work+0x8fb/0x15a0 worker_thread+0x576/0x1240 kthread+0x29d/0x340 ret_from_fork+0x1f/0x30

Freed by task 45: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 kasan_set_free_info+0x20/0x30 __kasan_slab_free+0xfb/0x130 kfree+0xac/0x350 hci_conn_cleanup+0x101/0x6a0 hci_conn_del+0x27e/0x6c0 hci_disconn_phylink_complete_evt+0xe0/0x120 hci_event_packet+0x812/0xe90 hci_rx_work+0x4d5/0xc50 process_one_work+0x8fb/0x15a0 worker_thread+0x576/0x1240 kthread+0x29d/0x340 ret_from_fork+0x1f/0x30

The buggy address belongs to the object at ffff88800c0f0500 The buggy address is located 24 bytes inside of which belongs to the cache kmalloc-128 of size 128 The buggy address belongs to the page: 128-byte region [ffff88800c0f0500, ffff88800c0f0580) flags: 0x100000000000200(slab|node=0|zone=1) page:00000000fe45cd86 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xc0f0 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 raw: 0100000000000200 ffffea00003a2c80 dead000000000004 ffff8880078418c0 page dumped because: kasan: bad access detected ffff88800c0f0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc Memory state around the buggy address: >ffff88800c0f0500: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88800c0f0480: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88800c0f0580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
Patch available.
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f63d24baff787e13b723d86fe036f84bdbc35045
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d404765dffdbd8dcd14758695d0c96c52fb2e624
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c41de54b0a963e59e4dd04c029a4a6d73f45ef9c
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b3c2ea1fd444b3bb7b82bfd2c3a45418f85c2502
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/684e505406abaeabe0058e9776f9210bf2747953
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/643a6c26bd32e339d00ad97b8822b6db009e803c
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4da302b90b96c309987eb9b37c8547f939f042d2
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3803d896ddd97c7c16689a5381c0960040727647
Web page

Bluetooth: Fix use after free in hci_send_acl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2cc803804ec9a296b3156855d6c8c4ca1c6b84be

Vendor Advisories for CVE-2022-49111(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-lts-xenial (4.4.0.289.295) @ xenial2026-10-28ubuntu
redhatkernel-0:4.18.0-372.151.1.el8_62025-07-09redhat
redhatkernel-rt-0:4.18.0-553.60.1.rt7.401.el8_102025-07-09redhat
redhatkernel-0:4.18.0-553.60.1.el8_102025-07-09redhat
redhatkernel-rt-0:5.14.0-70.136.1.rt21.208.el9_02025-07-02redhat
redhatkernel-0:4.18.0-193.156.1.el8_22025-07-02redhat
redhatkernel-0:4.18.0-477.100.1.el8_82025-07-02redhat
redhatkernel-0:5.14.0-70.136.1.el9_02025-07-01redhat
redhatkernel-0:4.18.0-305.161.1.el8_42025-07-01redhat
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 4.9.311 (fixes >=3.8.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (11 versions)
  • every version up to 5.10.113-1: fixed in 5.10.113-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-10-28 12:50 UTCEG score recompute
  7. 2026-10-28 12:50 UTCVendor advisory
  8. 2026-10-28 12:50 UTCGHSA enrichmentGHSA-5wpf-jxv5-j2rg · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-10-25 17:55 UTCEG score recompute
  12. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-21 05:36 UTCEG score recompute
  18. 2026-10-21 05:36 UTCVendor advisory
  19. 2026-10-21 05:36 UTCGHSA enrichmentGHSA-5wpf-jxv5-j2rg · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-10-19 11:55 UTCOSV refresh
  23. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  24. 2026-10-18 08:20 UTCEG score recompute
  25. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 74 more
  1. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-12 18:42 UTCEG score recompute
  6. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-11 22:05 UTCEG score recompute
  8. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-09-30 16:12 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-09-26 19:03 UTCOSV refresh
  21. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  25. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  26. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  27. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  28. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  29. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  30. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  31. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  32. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  33. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  34. 2026-09-07 04:48 UTCOSV refresh
  35. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  36. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  37. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  38. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  39. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  40. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  41. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  42. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  43. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  44. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  45. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  46. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  47. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  48. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  49. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  50. 2026-08-20 14:31 UTCOSV refresh
  51. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  53. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  54. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  56. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  59. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-08-05 09:35 UTCEG score recompute
  65. 2026-08-05 09:35 UTCVendor advisory
  66. 2026-08-05 09:35 UTCGHSA enrichmentGHSA-5wpf-jxv5-j2rg · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  68. 2026-08-04 11:17 UTCEG score recompute
  69. 2026-08-04 11:17 UTCVendor advisory
  70. 2026-08-04 11:17 UTCGHSA enrichmentGHSA-5wpf-jxv5-j2rg · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  72. 2026-08-04 09:47 UTCEG score recompute
  73. 2026-08-04 09:47 UTCVendor advisory
  74. 2026-08-04 09:47 UTCGHSA enrichmentGHSA-5wpf-jxv5-j2rg · GitHub severity HIGH · GitHub CVSS 7.8

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49111?
CVE-2022-49111 is a high-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use after free in hci_send_acl This fixes the following trace caused by receiving HCI_EV_DISCONN_PHY_LINK_COMPLETE which does call hci_conn_del without first checking if conn->type is in fact AMP_LINK and in case it…
When was the CVE record for CVE-2022-49111 published?
The CVE record for CVE-2022-49111 was published on February 26, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-49111 actively exploited?
CVE-2022-49111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49111?
CVE-2022-49111 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49111?
A fix for CVE-2022-49111 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49111 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49111

Explore →

Is Your Infrastructure Affected by CVE-2022-49111?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs