BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49111High confidence

Bluetooth: Fix use after free in hci_send_acl

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 10 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-55101

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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: <TASK> 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 </TASK> 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---

What

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: <TASK> 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 </TASK> 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---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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: <TASK> 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 </TASK> 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---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
an adjacent network → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2025-1905IBM QRadar SIEM Komponente: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM Komponenten ausnutzen, um Daten zu manipulieren, um einen Denial of Service Angriff durchzuführen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.

Official advisory
BSI · German · WID-SEC-W-2025-1430Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um beliebigen Programmcode auszuführen oder Informationen offenzulegen.

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0746Multiples vulnérabilités dans les produits IBM

ps://www.ibm.com/support/pages/node/7242161 Bulletin de sécurité IBM 7243372 du 28 août 2025 https://www.ibm.com/support/pages/node/7243372 Bulletin de sécurité IBM 7243373 du 28 août 2025 https://www.ibm.com/support/pages/node/7243373 Bulletin de sécurité IBM 7243411 du 28 août 2025 https://www.ibm.com/support/pages/node/7243411 Référence CVE CVE-2019-17543 https://www.cve.org/CVERecord?id=CVE-2019-17543 Référence CVE CVE-2019-5427 https://www.cve.org/CVERecord?id=CVE-2019-5427 Référence CVE CVE-2020-5260 https://www.cve.org/CVERecord?id=CVE-2020-5260 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49136 https://www.cve.org/CVERecord?id=CVE-2022-49136 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2024-10917 https://www.cve.org/CVERecord?id=CVE-2024-10917 Référence CVE CVE-2024-13009 https://www.cve.org/CVERecord?id=CVE-2024-13009 Référence CVE CVE-2024-21131 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0588Multiples vulnérabilités dans le noyau Linux de Red Hat

70 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10670 Bulletin de sécurité Red Hat RHSA-2025:10671 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10671 Bulletin de sécurité Red Hat RHSA-2025:10673 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10673 Bulletin de sécurité Red Hat RHSA-2025:10675 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10675 Bulletin de sécurité Red Hat RHSA-2025:10701 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10701 Bulletin de sécurité Red Hat RHSA-2025:10761 du 10 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10761 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49136 https://www.cve.org/CVERecord?id=CVE-2022-49136 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-50066 https://www.cve.org/CVERecord?id=CVE-2022-50066 Référence CVE CVE-2023-1652 https://www.cve.org/CVERecord?id=CVE-2023-1652 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52565 https://www.cve.org/CVERecord?id=CVE-2023-52565 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CV

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0561Multiples vulnérabilités dans le noyau Linux de Red Hat

in de sécurité Red Hat RHSA-2025:10009 du 01 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10009 Bulletin de sécurité Red Hat RHSA-2025:10174 du 01 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10174 Bulletin de sécurité Red Hat RHSA-2025:10179 du 02 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10179 Bulletin de sécurité Red Hat RHSA-2025:10193 du 02 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10193 Bulletin de sécurité Red Hat RHSA-2025:10211 du 02 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10211 Référence CVE CVE-2022-48919 https://www.cve.org/CVERecord?id=CVE-2022-48919 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49122 https://www.cve.org/CVERecord?id=CVE-2022-49122 Référence CVE CVE-2022-49328 https://www.cve.org/CVERecord?id=CVE-2022-49328 Référence CVE CVE-2022-49377 https://www.cve.org/CVERecord?id=CVE-2022-49377 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49407 https://www.cve.org/CVERecord?id=CVE-2022-49407 Référence CVE CVE-2023-1652 https://www.cve.org/CVERecord?id=CVE-2023-1652 Référence CVE CVE-2023-52623 https://www.cve.org/CVERecord?id=CV

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0449Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-47669 Référence CVE CVE-2021-47670 https://www.cve.org/CVERecord?id=CVE-2021-47670 Référence CVE CVE-2021-47671 https://www.cve.org/CVERecord?id=CVE-2021-47671 Référence CVE CVE-2022-48933 https://www.cve.org/CVERecord?id=CVE-2022-48933 Référence CVE CVE-2022-49044 https://www.cve.org/CVERecord?id=CVE-2022-49044 Référence CVE CVE-2022-49055 https://www.cve.org/CVERecord?id=CVE-2022-49055 Référence CVE CVE-2022-49060 https://www.cve.org/CVERecord?id=CVE-2022-49060 Référence CVE CVE-2022-49086 https://www.cve.org/CVERecord?id=CVE-2022-49086 Référence CVE CVE-2022-49110 https://www.cve.org/CVERecord?id=CVE-2022-49110 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49118 https://www.cve.org/CVERecord?id=CVE-2022-49118 Référence CVE CVE-2022-49121 https://www.cve.org/CVERecord?id=CVE-2022-49121 Référence CVE CVE-2022-49137 https://www.cve.org/CVERecord?id=CVE-2022-49137 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49171 https://www.cve.org/CVERecord?id=CVE-2022-49171 Référence CVE CVE-2022-49175 https://www.cve.org/CVERecord?id=CVE-2022-49175 Référence CVE CVE-2022-49176 https://www.cve.org/CVERecord?id=CVE-2022-49176 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49099 Référence CVE CVE-2022-49100 https://www.cve.org/CVERecord?id=CVE-2022-49100 Référence CVE CVE-2022-49102 https://www.cve.org/CVERecord?id=CVE-2022-49102 Référence CVE CVE-2022-49103 https://www.cve.org/CVERecord?id=CVE-2022-49103 Référence CVE CVE-2022-49104 https://www.cve.org/CVERecord?id=CVE-2022-49104 Référence CVE CVE-2022-49105 https://www.cve.org/CVERecord?id=CVE-2022-49105 Référence CVE CVE-2022-49106 https://www.cve.org/CVERecord?id=CVE-2022-49106 Référence CVE CVE-2022-49107 https://www.cve.org/CVERecord?id=CVE-2022-49107 Référence CVE CVE-2022-49109 https://www.cve.org/CVERecord?id=CVE-2022-49109 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49112 https://www.cve.org/CVERecord?id=CVE-2022-49112 Référence CVE CVE-2022-49113 https://www.cve.org/CVERecord?id=CVE-2022-49113 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49115 https://www.cve.org/CVERecord?id=CVE-2022-49115 Référence CVE CVE-2022-49116 https://www.cve.org/CVERecord?id=CVE-2022-49116 Référence CVE CVE-2022-49118 https://www.cve.org/CVERecord?id=CVE-2022-49118 Référence CVE CVE-2022-49119 https://www.cve.org/CVERecord?id=CVE-2022-49119 Référence CVE CVE-2022-49120 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49099 Référence CVE CVE-2022-49100 https://www.cve.org/CVERecord?id=CVE-2022-49100 Référence CVE CVE-2022-49102 https://www.cve.org/CVERecord?id=CVE-2022-49102 Référence CVE CVE-2022-49103 https://www.cve.org/CVERecord?id=CVE-2022-49103 Référence CVE CVE-2022-49104 https://www.cve.org/CVERecord?id=CVE-2022-49104 Référence CVE CVE-2022-49105 https://www.cve.org/CVERecord?id=CVE-2022-49105 Référence CVE CVE-2022-49106 https://www.cve.org/CVERecord?id=CVE-2022-49106 Référence CVE CVE-2022-49107 https://www.cve.org/CVERecord?id=CVE-2022-49107 Référence CVE CVE-2022-49109 https://www.cve.org/CVERecord?id=CVE-2022-49109 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49112 https://www.cve.org/CVERecord?id=CVE-2022-49112 Référence CVE CVE-2022-49113 https://www.cve.org/CVERecord?id=CVE-2022-49113 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49115 https://www.cve.org/CVERecord?id=CVE-2022-49115 Référence CVE CVE-2022-49116 https://www.cve.org/CVERecord?id=CVE-2022-49116 Référence CVE CVE-2022-49118 https://www.cve.org/CVERecord?id=CVE-2022-49118 Référence CVE CVE-2022-49119 https://www.cve.org/CVERecord?id=CVE-2022-49119 Référence CVE CVE-2022-49120 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0252Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49099 Référence CVE CVE-2022-49100 https://www.cve.org/CVERecord?id=CVE-2022-49100 Référence CVE CVE-2022-49102 https://www.cve.org/CVERecord?id=CVE-2022-49102 Référence CVE CVE-2022-49103 https://www.cve.org/CVERecord?id=CVE-2022-49103 Référence CVE CVE-2022-49104 https://www.cve.org/CVERecord?id=CVE-2022-49104 Référence CVE CVE-2022-49105 https://www.cve.org/CVERecord?id=CVE-2022-49105 Référence CVE CVE-2022-49106 https://www.cve.org/CVERecord?id=CVE-2022-49106 Référence CVE CVE-2022-49107 https://www.cve.org/CVERecord?id=CVE-2022-49107 Référence CVE CVE-2022-49109 https://www.cve.org/CVERecord?id=CVE-2022-49109 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49112 https://www.cve.org/CVERecord?id=CVE-2022-49112 Référence CVE CVE-2022-49113 https://www.cve.org/CVERecord?id=CVE-2022-49113 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49115 https://www.cve.org/CVERecord?id=CVE-2022-49115 Référence CVE CVE-2022-49116 https://www.cve.org/CVERecord?id=CVE-2022-49116 Référence CVE CVE-2022-49118 https://www.cve.org/CVERecord?id=CVE-2022-49118 Référence CVE CVE-2022-49119 https://www.cve.org/CVERecord?id=CVE-2022-49119 Référence CVE CVE-2022-49120 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < c41de54b0a963e59e4dd04c029a4a6d73f45ef9c; 9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < 643a6c26bd32e339d00ad97b8822b6db009e803c; 9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < 684e505406abaeabe0058e9776f9210bf2747953; 9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < 3803d896ddd97c7c16689a5381c0960040727647; 9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < 2cc803804ec9a296b3156855d6c8c4ca1c6b84be; 9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < d404765dffdbd8dcd14758695d0c96c52fb2e624; 9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < 4da302b90b96c309987eb9b37c8547f939f042d2; 9eef6b3a9e38d5f8ad315b2a7db153392e6a77d6 < b3c2ea1fd444b3bb7b82bfd2c3a45418f85c2502
Fixed
< 3.8; 4.9.311 ≤ 4.9.*; 4.14.276 ≤ 4.14.*; 4.19.238 ≤ 4.19.*; 5.4.189 ≤ 5.4.*; 5.10.111 ≤ 5.10.*; 5.15.34 ≤ 5.15.*; 5.16.20 ≤ 5.16.*
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 5 Aug 2026, 08:53 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-55101
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-55101↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49111 · cve.blacktree.nl