Review reviewHigh

CVE-2022-49910

Linux Linux, linux kernel

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 l...

CVSS
7.8
EPSS
0.30%
21.8% percentile
CISA KEV
Not listed
Published
2025.05.02
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.30%
Technical severityCVSS 7.8

Vulnerability overview

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 l...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < dc30e05bb18852303084430c03ca76e69257d9ea, >= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 03af22e23b96fb7ef75fb7885407ef457e8b403d, >= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 6c7407bfbeafc80a04e6eaedcf34d378532a04f2, >= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 4cd094fd5d872862ca278e15b9b51b07e915ef3f, >= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < cb1c012099ef5904cd468bdb8d6fcdfdd9bcb569, >= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 8278a87bb1eeea94350d675ef961ee5a03341fde, >= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 9a04161244603f502c6e453913e51edd59cb70c1, >= 4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 < 3aff8aaca4e36dc8b17eaa011684881a80238966, >= 3.6, >= 3.6 < 4.9.333, >= 4.10 < 4.14.299, >= 4.15 < 4.19.265, >= 4.20 < 5.4.224, >= 5.5 < 5.10.154, >= 5.11 < 5.15.78, >= 5.16 < 6.0.8, 6.1
Fixed versions
4.9.333, 4.14.299, 4.19.265, 5.4.224, 5.10.154, 5.15.78, 6.0.8

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416
CVE-2022-49910 — Linux Linux, linux kernel | SECUFOCUS NOW