Bug 2455334 (CVE-2026-31408) - CVE-2026-31408 kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold
Summary: CVE-2026-31408 kernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame()...
Keywords:
Status: NEW
Alias: CVE-2026-31408
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-06 09:01 UTC by OSIDB Bzimport
Modified: 2026-05-28 13:26 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:19569 0 None None None 2026-05-20 12:15:50 UTC
Red Hat Product Errata RHSA-2026:21556 0 None None None 2026-05-28 01:24:00 UTC
Red Hat Product Errata RHSA-2026:21706 0 None None None 2026-05-28 08:26:00 UTC
Red Hat Product Errata RHSA-2026:21745 0 None None None 2026-05-28 13:26:24 UTC

Description OSIDB Bzimport 2026-04-06 09:01:27 UTC
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold

sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately
releases the lock without holding a reference to the socket. A concurrent
close() can free the socket between the lock release and the subsequent
sk->sk_state access, resulting in a use-after-free.

Other functions in the same file (sco_sock_timeout(), sco_conn_del())
correctly use sco_sock_hold() to safely hold a reference under the lock.

Fix by using sco_sock_hold() to take a reference before releasing the
lock, and adding sock_put() on all exit paths.

Comment 3 errata-xmlrpc 2026-05-20 12:15:49 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:19569 https://access.redhat.com/errata/RHSA-2026:19569

Comment 4 errata-xmlrpc 2026-05-28 01:23:59 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:21556 https://access.redhat.com/errata/RHSA-2026:21556

Comment 5 errata-xmlrpc 2026-05-28 08:25:59 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:21706 https://access.redhat.com/errata/RHSA-2026:21706

Comment 6 errata-xmlrpc 2026-05-28 13:26:23 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:21745 https://access.redhat.com/errata/RHSA-2026:21745


Note You need to log in before you can comment on or make changes to this bug.