BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49910High confidence

Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.27% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-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 Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2022-49910 · CSAF 2.0 · revision 52 · interimSUSE Product Security TeamCVE-2022-49910
292 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu Fix the race condition between the following two flows that run in parallel: 1. l2cap_reassemble_sdu -> chan->ops->recv (l2cap_sock_recv_cb) -> __sock_queue_rcv_skb. 2. bt_sock_recvmsg -> skb_recv_datagram, skb_free_datagram. An SKB can be queued by the first flow and immediately dequeued and freed by the second flow, therefore the callers of l2cap_reassemble_sdu can't use the SKB after that function returns. However, some places continue accessing struct l2cap_ctrl that resides in the SKB's CB for a short time after l2cap_reassemble_sdu returns, leading to a use-after-free condition (the stack trace is below, line numbers for kernel 5.19.8). Fix it by keeping a local copy of struct l2cap_ctrl. BUG: KASAN: use-after-free in l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth Read of size 1 at addr ffff88812025f2f0 by task kworker/u17:3/43169 Workqueue: hci0 hci_rx_work [bluetooth] Call Trace: dump_stack_lvl (lib/dump_stack.c:107 (discriminator 4)) print_report.cold (mm/kasan/report.c:314 mm/kasan/report.c:429) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth kasan_report (mm/kasan/report.c:162 mm/kasan/report.c:493) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx (net/bluetooth/l2cap_core.c:7236 net/bluetooth/l2cap_core.c:7271) bluetooth ret_from_fork (arch/x86/entry/entry_64.S:306) Allocated by task 43169: kasan_save_stack (mm/kasan/common.c:39) __kasan_slab_alloc (mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:469) kmem_cache_alloc_node (mm/slab.h:750 mm/slub.c:3243 mm/slub.c:3293) __alloc_skb (net/core/skbuff.c:414) l2cap_recv_frag (./include/net/bluetooth/bluetooth.h:425 net/bluetooth/l2cap_core.c:8329) bluetooth l2cap_recv_acldata (net/bluetooth/l2cap_core.c:8442) bluetooth hci_rx_work (net/bluetooth/hci_core.c:3642 net/bluetooth/hci_core.c:3832) bluetooth process_one_work (kernel/workqueue.c:2289) worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2437) kthread (kernel/kthread.c:376) ret_from_fork (arch/x86/entry/entry_64.S:306) Freed by task 27920: kasan_save_stack (mm/kasan/common.c:39) kasan_set_track (mm/kasan/common.c:45) kasan_set_free_info (mm/kasan/generic.c:372) ____kasan_slab_free (mm/kasan/common.c:368 mm/kasan/common.c:328) slab_free_freelist_hook (mm/slub.c:1780) kmem_cache_free (mm/slub.c:3536 mm/slub.c:3553) skb_free_datagram (./include/net/sock.h:1578 ./include/net/sock.h:1639 net/core/datagram.c:323) bt_sock_recvmsg (net/bluetooth/af_bluetooth.c:295) bluetooth l2cap_sock_recvmsg (net/bluetooth/l2cap_sock.c:1212) bluetooth sock_read_iter (net/socket.c:1087) new_sync_read (./include/linux/fs.h:2052 fs/read_write.c:401) vfs_read (fs/read_write.c:482) ksys_read (fs/read_write.c:620) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2022-49910 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu
49 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-rt as a component of Red Hat Enterprise Linux 7
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 7
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 7
  • kernel-rt-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt-doc as a component of Red Hat Enterprise Linux 7
  • kernel-rt-kvm as a component of Red Hat Enterprise Linux 7
  • kernel-rt-trace as a component of Red Hat Enterprise Linux 7
  • kernel-rt-trace-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt-trace-kvm as a component of Red Hat Enterprise Linux 7
  • kernel-rt.src as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 8
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu Fix the race condition between the following two flows that run in parallel: 1. l2cap_reassemble_sdu -> chan->ops->recv (l2cap_sock_recv_cb) -> __sock_queue_rcv_skb. 2. bt_sock_recvmsg -> skb_recv_datagram, skb_free_datagram. An SKB can be queued by the first flow and immediately dequeued and freed by the second flow, therefore the callers of l2cap_reassemble_sdu can't use the SKB after that function returns. However, some places continue accessing struct l2cap_ctrl that resides in the SKB's CB for a short time after l2cap_reassemble_sdu returns, leading to a use-after-free condition (the stack trace is below, line numbers for kernel 5.19.8). Fix it by keeping a local copy of struct l2cap_ctrl. BUG: KASAN: use-after-free in l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth Read of size 1 at addr ffff88812025f2f0 by task kworker/u17:3/43169 Workqueue: hci0 hci_rx_work [bluetooth] Call Trace: dump_stack_lvl (lib/dump_stack.c:107 (discriminator 4)) print_report.cold (mm/kasan/report.c:314 mm/kasan/report.c:429) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth kasan_report (mm/kasan/report.c:162 mm/kasan/report.c:493) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx (net/bluetooth/l2cap_core.c:7236 net/bluetooth/l2cap_core.c:7271) bluetooth ret_from_fork (arch/x86/entry/entry_64.S:306) Allocated by task 43169: kasan_save_stack (mm/kasan/common.c:39) __kasan_slab_alloc (mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:469) kmem_cache_alloc_node (mm/slab.h:750 mm/slub.c:3243 mm/slub.c:3293) __alloc_skb (net/core/skbuff.c:414) l2cap_recv_frag (./include/net/bluetooth/bluetooth.h:425 net/bluetooth/l2cap_core.c:8329) bluetooth l2cap_recv_acldata (net/bluetooth/l2cap_core.c:8442) bluetooth hci_rx_work (net/bluetooth/hci_core.c:3642 net/bluetooth/hci_core.c:3832) bluetooth process_one_work (kernel/workqueue.c:2289) worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2437) kthread (kernel/kthread.c:376) ret_from_fork (arch/x86/entry/entry_64.S:306) Freed by task 27920: kasan_save_stack (mm/kasan/common.c:39) kasan_set_track (mm/kasan/common.c:45) kasan_set_free_info (mm/kasan/generic.c:372) ____kasan_slab_free (mm/kasan/common.c:368 mm/kasan/common.c:328) slab_free_freelist_hook (mm/slub.c:1780) kmem_cache_free (mm/slub.c:3536 mm/slub.c:3553) skb_free_datagram (./include/net/sock.h:1578 ./include/net/sock.h:1639 net/core/datagram.c:323) bt_sock_recvmsg (net/bluetooth/af_bluetooth.c:295) bluetooth l2cap_sock_recvmsg (net/bluetooth/l2cap_sock.c:1212) bluetooth sock_read_iter (net/socket.c:1087) new_sync_read (./include/linux/fs.h:2052 fs/read_write.c:401) vfs_read (fs/read_write.c:482) ksys_read (fs/read_write.c:620) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-2025-12858

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 actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu Fix the race condition between the following two flows that run in parallel: 1. l2cap_reassemble_sdu -> chan->ops->recv (l2cap_sock_recv_cb) -> __sock_queue_rcv_skb. 2. bt_sock_recvmsg -> skb_recv_datagram, skb_free_datagram. An SKB can be queued by the first flow and immediately dequeued and freed by the second flow, therefore the callers of l2cap_reassemble_sdu can't use the SKB after that function returns. However, some places continue accessing struct l2cap_ctrl that resides in the SKB's CB for a short time after l2cap_reassemble_sdu returns, leading to a use-after-free condition (the stack trace is below, line numbers for kernel 5.19.8). Fix it by keeping a local copy of struct l2cap_ctrl. BUG: KASAN: use-after-free in l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth Read of size 1 at addr ffff88812025f2f0 by task kworker/u17:3/43169 Workqueue: hci0 hci_rx_work [bluetooth] Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:107 (discriminator 4)) print_report.cold (mm/kasan/report.c:314 mm/kasan/report.c:429) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth kasan_report (mm/kasan/report.c:162 mm/kasan/report.c:493) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx (net/bluetooth/l2cap_core.c:7236 net/bluetooth/l2cap_core.c:7271) bluetooth ret_from_fork (arch/x86/entry/entry_64.S:306) </TASK> Allocated by task 43169: kasan_save_stack (mm/kasan/common.c:39) __kasan_slab_alloc (mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:469) kmem_cache_alloc_node (mm/slab.h:750 mm/slub.c:3243 mm/slub.c:3293) __alloc_skb (net/core/skbuff.c:414) l2cap_recv_frag (./include/net/bluetooth/bluetooth.h:425 net/bluetooth/l2cap_core.c:8329) bluetooth l2cap_recv_acldata (net/bluetooth/l2cap_core.c:8442) bluetooth hci_rx_work (net/bluetooth/hci_core.c:3642 net/bluetooth/hci_core.c:3832) bluetooth process_one_work (kernel/workqueue.c:2289) worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2437) kthread (kernel/kthread.c:376) ret_from_fork (arch/x86/entry/entry_64.S:306) Freed by task 27920: kasan_save_stack (mm/kasan/common.c:39) kasan_set_track (mm/kasan/common.c:45) kasan_set_free_info (mm/kasan/generic.c:372) ____kasan_slab_free (mm/kasan/common.c:368 mm/kasan/common.c:328) slab_free_freelist_hook (mm/slub.c:1780) kmem_cache_free (mm/slub.c:3536 mm/slub.c:3553) skb_free_datagram (./include/net/sock.h:1578 ./include/net/sock.h:1639 net/core/datagram.c:323) bt_sock_recvmsg (net/bluetooth/af_bluetooth.c:295) bluetooth l2cap_sock_recvmsg (net/bluetooth/l2cap_sock.c:1212) bluetooth sock_read_iter (net/socket.c:1087) new_sync_read (./include/linux/fs.h:2052 fs/read_write.c:401) vfs_read (fs/read_write.c:482) ksys_read (fs/read_write.c:620) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu Fix the race condition between the following two flows that run in parallel: 1. l2cap_reassemble_sdu -> chan->ops->recv (l2cap_sock_recv_cb) -> __sock_queue_rcv_skb. 2. bt_sock_recvmsg -> skb_recv_datagram, skb_free_datagram. An SKB can be queued by the first flow and immediately dequeued and freed by the second flow, therefore the callers of l2cap_reassemble_sdu can't use the SKB after that function returns. However, some places continue accessing struct l2cap_ctrl that resides in the SKB's CB for a short time after l2cap_reassemble_sdu returns, leading to a use-after-free condition (the stack trace is below, line numbers for kernel 5.19.8). Fix it by keeping a local copy of struct l2cap_ctrl. BUG: KASAN: use-after-free in l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth Read of size 1 at addr ffff88812025f2f0 by task kworker/u17:3/43169 Workqueue: hci0 hci_rx_work [bluetooth] Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:107 (discriminator 4)) print_report.cold (mm/kasan/report.c:314 mm/kasan/report.c:429) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth kasan_report (mm/kasan/report.c:162 mm/kasan/report.c:493) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx (net/bluetooth/l2cap_core.c:7236 net/bluetooth/l2cap_core.c:7271) bluetooth ret_from_fork (arch/x86/entry/entry_64.S:306) </TASK> Allocated by task 43169: kasan_save_stack (mm/kasan/common.c:39) __kasan_slab_alloc (mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:469) kmem_cache_alloc_node (mm/slab.h:750 mm/slub.c:3243 mm/slub.c:3293) __alloc_skb (net/core/skbuff.c:414) l2cap_recv_frag (./include/net/bluetooth/bluetooth.h:425 net/bluetooth/l2cap_core.c:8329) bluetooth l2cap_recv_acldata (net/bluetooth/l2cap_core.c:8442) bluetooth hci_rx_work (net/bluetooth/hci_core.c:3642 net/bluetooth/hci_core.c:3832) bluetooth process_one_work (kernel/workqueue.c:2289) worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2437) kthread (kernel/kthread.c:376) ret_from_fork (arch/x86/entry/entry_64.S:306) Freed by task 27920: kasan_save_stack (mm/kasan/common.c:39) kasan_set_track (mm/kasan/common.c:45) kasan_set_free_info (mm/kasan/generic.c:372) ____kasan_slab_free (mm/kasan/common.c:368 mm/kasan/common.c:328) slab_free_freelist_hook (mm/slub.c:1780) kmem_cache_free (mm/slub.c:3536 mm/slub.c:3553) skb_free_datagram (./include/net/sock.h:1578 ./include/net/sock.h:1639 net/core/datagram.c:323) bt_sock_recvmsg (net/bluetooth/af_bluetooth.c:295) bluetooth l2cap_sock_recvmsg (net/bluetooth/l2cap_sock.c:1212) bluetooth sock_read_iter (net/socket.c:1087) new_sync_read (./include/linux/fs.h:2052 fs/read_write.c:401) vfs_read (fs/read_write.c:482) ksys_read (fs/read_write.c:620) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)

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: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu Fix the race condition between the following two flows that run in parallel: 1. l2cap_reassemble_sdu -> chan->ops->recv (l2cap_sock_recv_cb) -> __sock_queue_rcv_skb. 2. bt_sock_recvmsg -> skb_recv_datagram, skb_free_datagram. An SKB can be queued by the first flow and immediately dequeued and freed by the second flow, therefore the callers of l2cap_reassemble_sdu can't use the SKB after that function returns. However, some places continue accessing struct l2cap_ctrl that resides in the SKB's CB for a short time after l2cap_reassemble_sdu returns, leading to a use-after-free condition (the stack trace is below, line numbers for kernel 5.19.8). Fix it by keeping a local copy of struct l2cap_ctrl. BUG: KASAN: use-after-free in l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth Read of size 1 at addr ffff88812025f2f0 by task kworker/u17:3/43169 Workqueue: hci0 hci_rx_work [bluetooth] Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:107 (discriminator 4)) print_report.cold (mm/kasan/report.c:314 mm/kasan/report.c:429) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth kasan_report (mm/kasan/report.c:162 mm/kasan/report.c:493) ? l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx_state_recv (net/bluetooth/l2cap_core.c:6906) bluetooth l2cap_rx (net/bluetooth/l2cap_core.c:7236 net/bluetooth/l2cap_core.c:7271) bluetooth ret_from_fork (arch/x86/entry/entry_64.S:306) </TASK> Allocated by task 43169: kasan_save_stack (mm/kasan/common.c:39) __kasan_slab_alloc (mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:469) kmem_cache_alloc_node (mm/slab.h:750 mm/slub.c:3243 mm/slub.c:3293) __alloc_skb (net/core/skbuff.c:414) l2cap_recv_frag (./include/net/bluetooth/bluetooth.h:425 net/bluetooth/l2cap_core.c:8329) bluetooth l2cap_recv_acldata (net/bluetooth/l2cap_core.c:8442) bluetooth hci_rx_work (net/bluetooth/hci_core.c:3642 net/bluetooth/hci_core.c:3832) bluetooth process_one_work (kernel/workqueue.c:2289) worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2437) kthread (kernel/kthread.c:376) ret_from_fork (arch/x86/entry/entry_64.S:306) Freed by task 27920: kasan_save_stack (mm/kasan/common.c:39) kasan_set_track (mm/kasan/common.c:45) kasan_set_free_info (mm/kasan/generic.c:372) ____kasan_slab_free (mm/kasan/common.c:368 mm/kasan/common.c:328) slab_free_freelist_hook (mm/slub.c:1780) kmem_cache_free (mm/slub.c:3536 mm/slub.c:3553) skb_free_datagram (./include/net/sock.h:1578 ./include/net/sock.h:1639 net/core/datagram.c:323) bt_sock_recvmsg (net/bluetooth/af_bluetooth.c:295) bluetooth l2cap_sock_recvmsg (net/bluetooth/l2cap_sock.c:1212) bluetooth sock_read_iter (net/socket.c:1087) new_sync_read (./include/linux/fs.h:2052 fs/read_write.c:401) vfs_read (fs/read_write.c:482) ksys_read (fs/read_write.c:620) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)

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.

Cyber Security Agency of Singapore · English · CSA-SB-20250507Security Bulletin 07 May 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 07 May 2025, published on 7 May 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49766 Référence CVE CVE-2022-49773 https://www.cve.org/CVERecord?id=CVE-2022-49773 Référence CVE CVE-2022-49783 https://www.cve.org/CVERecord?id=CVE-2022-49783 Référence CVE CVE-2022-49803 https://www.cve.org/CVERecord?id=CVE-2022-49803 Référence CVE CVE-2022-49810 https://www.cve.org/CVERecord?id=CVE-2022-49810 Référence CVE CVE-2022-49829 https://www.cve.org/CVERecord?id=CVE-2022-49829 Référence CVE CVE-2022-49833 https://www.cve.org/CVERecord?id=CVE-2022-49833 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49901 https://www.cve.org/CVERecord?id=CVE-2022-49901 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49932 https://www.cve.org/CVERecord?id=CVE-2022-49932 Référence CVE CVE-2022-49935 https://www.cve.org/CVERecord?id=CVE-2022-49935 Référence CVE CVE-2022-49940 https://www.cve.org/CVERecord?id=CVE-2022-49940 Référence CVE CVE-2022-49943 https://www.cve.org/CVERecord?id=CVE-2022-49943 Référence CVE CVE-2022-49955 https://www.cve.org/CVERecord?id=CVE-2022-49955 Référence CVE CVE-2022-49961 https://www.cve.org/CVERecord?id=CVE-2022-49961 Référence CVE CVE-2022-49965 https://www.cve.org/CVERecord?id=CVE-2022-49965 Référence CVE CVE-2022-49967 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49766 Référence CVE CVE-2022-49773 https://www.cve.org/CVERecord?id=CVE-2022-49773 Référence CVE CVE-2022-49783 https://www.cve.org/CVERecord?id=CVE-2022-49783 Référence CVE CVE-2022-49803 https://www.cve.org/CVERecord?id=CVE-2022-49803 Référence CVE CVE-2022-49810 https://www.cve.org/CVERecord?id=CVE-2022-49810 Référence CVE CVE-2022-49829 https://www.cve.org/CVERecord?id=CVE-2022-49829 Référence CVE CVE-2022-49833 https://www.cve.org/CVERecord?id=CVE-2022-49833 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49901 https://www.cve.org/CVERecord?id=CVE-2022-49901 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49932 https://www.cve.org/CVERecord?id=CVE-2022-49932 Référence CVE CVE-2022-49935 https://www.cve.org/CVERecord?id=CVE-2022-49935 Référence CVE CVE-2022-49940 https://www.cve.org/CVERecord?id=CVE-2022-49940 Référence CVE CVE-2022-49943 https://www.cve.org/CVERecord?id=CVE-2022-49943 Référence CVE CVE-2022-49955 https://www.cve.org/CVERecord?id=CVE-2022-49955 Référence CVE CVE-2022-49961 https://www.cve.org/CVERecord?id=CVE-2022-49961 Référence CVE CVE-2022-49965 https://www.cve.org/CVERecord?id=CVE-2022-49965 Référence CVE CVE-2022-49967 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49889 Référence CVE CVE-2022-49890 https://www.cve.org/CVERecord?id=CVE-2022-49890 Référence CVE CVE-2022-49891 https://www.cve.org/CVERecord?id=CVE-2022-49891 Référence CVE CVE-2022-49892 https://www.cve.org/CVERecord?id=CVE-2022-49892 Référence CVE CVE-2022-49900 https://www.cve.org/CVERecord?id=CVE-2022-49900 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=CVE-2022-49924 Référence CVE CVE-2022-49925 https://www.cve.org/CVERecord?id=CVE-2022-49925 Référence CVE CVE-2022-49927 https://www.cve.org/CVERecord?id=CVE-2022-49927 Référence CVE CVE-2022-49928 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49891 Référence CVE CVE-2022-49892 https://www.cve.org/CVERecord?id=CVE-2022-49892 Référence CVE CVE-2022-49900 https://www.cve.org/CVERecord?id=CVE-2022-49900 Référence CVE CVE-2022-49901 https://www.cve.org/CVERecord?id=CVE-2022-49901 Référence CVE CVE-2022-49902 https://www.cve.org/CVERecord?id=CVE-2022-49902 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=CVE-2022-49917 Référence CVE CVE-2022-49918 https://www.cve.org/CVERecord?id=CVE-2022-49918 Référence CVE CVE-2022-49921 https://www.cve.org/CVERecord?id=CVE-2022-49921 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49889 Référence CVE CVE-2022-49890 https://www.cve.org/CVERecord?id=CVE-2022-49890 Référence CVE CVE-2022-49891 https://www.cve.org/CVERecord?id=CVE-2022-49891 Référence CVE CVE-2022-49892 https://www.cve.org/CVERecord?id=CVE-2022-49892 Référence CVE CVE-2022-49900 https://www.cve.org/CVERecord?id=CVE-2022-49900 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=CVE-2022-49924 Référence CVE CVE-2022-49925 https://www.cve.org/CVERecord?id=CVE-2022-49925 Référence CVE CVE-2022-49927 https://www.cve.org/CVERecord?id=CVE-2022-49927 Référence CVE CVE-2022-49928 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49891 Référence CVE CVE-2022-49892 https://www.cve.org/CVERecord?id=CVE-2022-49892 Référence CVE CVE-2022-49900 https://www.cve.org/CVERecord?id=CVE-2022-49900 Référence CVE CVE-2022-49901 https://www.cve.org/CVERecord?id=CVE-2022-49901 Référence CVE CVE-2022-49902 https://www.cve.org/CVERecord?id=CVE-2022-49902 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=CVE-2022-49917 Référence CVE CVE-2022-49918 https://www.cve.org/CVERecord?id=CVE-2022-49918 Référence CVE CVE-2022-49921 https://www.cve.org/CVERecord?id=CVE-2022-49921 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49898 Référence CVE CVE-2022-49900 https://www.cve.org/CVERecord?id=CVE-2022-49900 Référence CVE CVE-2022-49901 https://www.cve.org/CVERecord?id=CVE-2022-49901 Référence CVE CVE-2022-49902 https://www.cve.org/CVERecord?id=CVE-2022-49902 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49907 https://www.cve.org/CVERecord?id=CVE-2022-49907 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49913 https://www.cve.org/CVERecord?id=CVE-2022-49913 Référence CVE CVE-2022-49914 https://www.cve.org/CVERecord?id=CVE-2022-49914 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=CVE-2022-49917 Référence CVE CVE-2022-49918 https://www.cve.org/CVERecord?id=CVE-2022-49918 Référence CVE CVE-2022-49921 https://www.cve.org/CVERecord?id=CVE-2022-49921 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49889 Référence CVE CVE-2022-49890 https://www.cve.org/CVERecord?id=CVE-2022-49890 Référence CVE CVE-2022-49891 https://www.cve.org/CVERecord?id=CVE-2022-49891 Référence CVE CVE-2022-49892 https://www.cve.org/CVERecord?id=CVE-2022-49892 Référence CVE CVE-2022-49900 https://www.cve.org/CVERecord?id=CVE-2022-49900 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=CVE-2022-49924 Référence CVE CVE-2022-49925 https://www.cve.org/CVERecord?id=CVE-2022-49925 Référence CVE CVE-2022-49927 https://www.cve.org/CVERecord?id=CVE-2022-49927 Référence CVE CVE-2022-49928 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026721Linux の Linux Kernel における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

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.
Fix availability varies by product
Affected
Linux: 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < dc30e05bb18852303084430c03ca76e69257d9ea, 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 03af22e23b96fb7ef75fb7885407ef457e8b403d, 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 6c7407bfbeafc80a04e6eaedcf34d378532a04f2, 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 4cd094fd5d872862ca278e15b9b51b07e915ef3f, 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < cb1c012099ef5904cd468bdb8d6fcdfdd9bcb569, 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 8278a87bb1eeea94350d675ef961ee5a03341fde, 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 9a04161244603f502c6e453913e51edd59cb70c1, 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 3aff8aaca4e36dc8b17eaa011684881a80238966, 3.6
Fixed
Linux: < 3.6, 4.9.333 ≤ 4.9.*, 4.14.299 ≤ 4.14.*, 4.19.265 ≤ 4.19.*, 5.4.224 ≤ 5.4.*, 5.10.154 ≤ 5.10.*, 5.15.78 ≤ 5.15.*, 6.0.8 ≤ 6.0.*, 6.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 May 2025 · Last source change 5 Aug 2026, 08:56 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-2025-12858
Product sourceCNA
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    bpftool as a component of Red Hat Enterprise Linux 7; kernel as a component of Red Hat Enterprise Linux 7; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7; kernel-bootwrapper as a component of Red Hat Enterprise Linux 7; kernel-debug as a component of Red Hat Enterprise Linux 7; kernel-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-devel as a component of Red Hat Enterprise Linux 7; kernel-doc as a component of Red Hat Enterprise Linux 7; kernel-headers as a component of Red Hat Enterprise Linux 7; kernel-kdump as a component of Red Hat Enterprise Linux 7; kernel-kdump-devel as a component of Red Hat Enterprise Linux 7; kernel-rt as a component of Red Hat Enterprise Linux 7; kernel-rt-debug as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-doc as a component of Red Hat Enterprise Linux 7; kernel-rt-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-trace as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt.src as a component of Red Hat Enterprise Linux 7; kernel-tools as a component of Red Hat Enterprise Linux 7; kernel-tools-libs as a component of Red Hat Enterprise Linux 7; kernel-tools-libs-devel as a component of Red Hat Enterprise Linux 7; kernel.src as a component of Red Hat Enterprise Linux 7; perf as a component of Red Hat Enterprise Linux 7; python-perf as a component of Red Hat Enterprise Linux 7; bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; and 154 more · Fixed: bpftool-debuginfo-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; kernel-debug-debuginfo-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; kernel-debuginfo-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; kernel-debuginfo-common-x86_64-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; kernel-devel-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; kernel-tools-debuginfo-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; perf-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; perf-debuginfo-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; python3-perf-debuginfo-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8; bpftool-0:4.18.0-372.57.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); bpftool-0:4.18.0-372.57.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); bpftool-0:4.18.0-372.57.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); bpftool-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); bpftool-debuginfo-0:4.18.0-372.57.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); bpftool-debuginfo-0:4.18.0-372.57.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); bpftool-debuginfo-0:4.18.0-372.57.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); bpftool-debuginfo-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-0:4.18.0-372.57.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-0:4.18.0-372.57.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-0:4.18.0-372.57.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-0:4.18.0-372.57.1.el8_6.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-abi-stablelists-0:4.18.0-372.57.1.el8_6.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-core-0:4.18.0-372.57.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-core-0:4.18.0-372.57.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-core-0:4.18.0-372.57.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-core-0:4.18.0-372.57.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-debug-0:4.18.0-372.57.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-debug-0:4.18.0-372.57.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); kernel-debug-0:4.18.0-372.57.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6); and 99 more
    After
    kernel-rt as a component of Red Hat Enterprise Linux 7; kernel-rt-debug as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-doc as a component of Red Hat Enterprise Linux 7; kernel-rt-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-trace as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt.src as a component of Red Hat Enterprise Linux 7; kernel-rt as a component of Red Hat Enterprise Linux 8; kernel-rt-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-rt-devel as a component of Red Hat Enterprise Linux 8; kernel-rt-kvm as a component of Red Hat Enterprise Linux 8; kernel-rt-modules as a component of Red Hat Enterprise Linux 8; kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 8; kernel-rt.src as a component of Red Hat Enterprise Linux 8; kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug as a component of Red Hat Enterprise Linux 9; and 19 more · Fixed: bpftool-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); bpftool-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-0:3.10.0-1160.95.1.el7.src as a component of Red Hat Enterprise Linux Client (v. 7); kernel-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-abi-whitelists-0:3.10.0-1160.95.1.el7.noarch as a component of Red Hat Enterprise Linux Client (v. 7); kernel-debug-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-debug-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-debug-devel-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-debuginfo-common-x86_64-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-devel-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-doc-0:3.10.0-1160.95.1.el7.noarch as a component of Red Hat Enterprise Linux Client (v. 7); kernel-tools-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-tools-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); kernel-tools-libs-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); perf-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); perf-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); python-perf-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); python-perf-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); bpftool-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); kernel-debug-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); kernel-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); kernel-debuginfo-common-x86_64-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); kernel-tools-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); kernel-tools-libs-devel-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); perf-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); python-perf-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bpftool-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7); kernel-debug-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7); kernel-debuginfo-0:3.10.0-1160.95.1.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7); and 540 more
    Red Hat Product Security ↗
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-2025-12858↗Vendor CSAF · SUSE Product Security Team↗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-49910 · cve.blacktree.nl