Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2025-68304— Bluetooth: hci_core: lookup hci_conn on RX path on protocol side

CVSS 8.8 · High EPSS 0.20% · P10

Affected Version Matrix 12

VendorProductVersion RangeStatus
LinuxLinux5af1f84ed13a416297ab9ced7537f4d5ae7f329a< ec74cdf77310c43b01b83ee898a9bd4b4b0b8e93affected
5af1f84ed13a416297ab9ced7537f4d5ae7f329a< 79a2d4678ba90bdba577dc3af88cc900d6dcd5eeaffected
cd55c13bbb3d093ae601aa97e588ed4c1390ebb1affected
4d3ca4a9aaf0aa798a6be372dc0fc3a29e37dd57affected
80265dd1d944c3f33e52375b5dbe654980bd2688affected
6.1.149< 6.2affected
6.4.16< 6.5affected
6.5.3< 6.6affected
… +4 more rows
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-68304

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Bluetooth: hci_core: lookup hci_conn on RX path on protocol side
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: lookup hci_conn on RX path on protocol side The hdev lock/lookup/unlock/use pattern in the packet RX path doesn't ensure hci_conn* is not concurrently modified/deleted. This locking appears to be leftover from before conn_hash started using RCU commit bf4c63252490b ("Bluetooth: convert conn hash to RCU") and not clear if it had purpose since then. Currently, there are code paths that delete hci_conn* from elsewhere than the ordered hdev->workqueue where the RX work runs in. E.g. commit 5af1f84ed13a ("Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync") introduced some of these, and there probably were a few others before it. It's better to do the locking so that even if these run concurrently no UAF is possible. Move the lookup of hci_conn and associated socket-specific conn to protocol recv handlers, and do them within a single critical section to cover hci_conn* usage and lookup. syzkaller has reported a crash that appears to be this issue: [Task hdev->workqueue] [Task 2] hci_disconnect_all_sync l2cap_recv_acldata(hcon) hci_conn_get(hcon) hci_abort_conn_sync(hcon) hci_dev_lock hci_dev_lock hci_conn_del(hcon) v-------------------------------- hci_dev_unlock hci_conn_put(hcon) conn = hcon->l2cap_data (UAF)
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于并发修改可能导致释放后重用。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 5af1f84ed13a416297ab9ced7537f4d5ae7f329a ~ ec74cdf77310c43b01b83ee898a9bd4b4b0b8e93 -
LinuxLinux 6.6 -

II. Public POCs for CVE-2025-68304

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-68304

请登录查看更多情报信息。

Other References for CVE-2025-68304 (2)

Same Patch Batch · Linux · 2025-12-16 · 157 CVEs total

CVE-2025-682639.8 CRITICALksmbd: ipc: fix use-after-free in ipc_msg_send_request
CVE-2025-683019.8 CRITICALnet: atlantic: fix fragment overflow handling in RX path
CVE-2025-403509.8 CRITICALnet/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ
CVE-2025-682849.8 CRITICALlibceph: prevent potential out-of-bounds writes in handle_auth_session_key()
CVE-2025-682859.8 CRITICALlibceph: fix potential use-after-free in have_mon_and_osd_map()
CVE-2025-681929.8 CRITICALnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup
CVE-2025-683159.8 CRITICALf2fs: fix to detect potential corrupted nid in free_nid_list
CVE-2025-682558.8 HIGHstaging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing
CVE-2025-682568.8 HIGHstaging: rtl8723bs: fix out-of-bounds read in rtw_get_ie() parser
CVE-2025-682268.8 HIGHsmb: client: fix incomplete backport in cfids_invalidation_worker()
CVE-2025-403628.8 HIGHceph: fix multifs mds auth caps issue
CVE-2025-683148.8 HIGHdrm/msm: make sure last_fence is always updated
CVE-2025-682508.2 HIGHhung_task: fix warnings caused by unaligned lock pointers
CVE-2025-682947.8 HIGHio_uring/net: ensure vectored buffer node import is tied to notification
CVE-2025-681747.8 HIGHamd/amdkfd: enhance kfd process check in switch partition
CVE-2025-681757.8 HIGHmedia: nxp: imx8-isi: Fix streaming cleanup on release
CVE-2025-681797.8 HIGHs390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP
CVE-2025-681897.8 HIGHdrm/msm: Fix GEM free for imported dma-bufs
CVE-2025-683037.8 HIGHplatform/x86: intel: punit_ipc: fix memory corruption
CVE-2025-681837.8 HIGHima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr

Showing top 20 of 157 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2025-68304

No comments yet

Leave a comment