CVE-2026-97976 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel-based systems, particularly those utilizing Bluetooth functionality, should assess exposure and prioritize patching. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review system configurations, monitor system logs, and verify Linux kernel versions to ensure the patch is applied. Additionally, defenders should consider compensating controls for exposed

Why it matters

A vulnerability in the Linux kernel's Bluetooth component has been addressed, and defenders should prioritize verifying the Linux kernel version and applying patches to address this vulnerability.

• Potential out-of-bounds read in btintel_pcie_submit_rx_work()
• Verification of Linux kernel version and patch application required
• Monitoring system logs for potential exploitation attempts recommended

Technical summary

The btintel_pcie_submit_rx_work() function in the Linux kernel's Bluetooth component did not validate the packet_len field from the rfh_hdr before passing it to skb_put_data(), potentially leading to an out-of-bounds read. This issue can be simulated by using customized firmware or modifying the rfh_hdr->packet_len in the driver. Affected systems include Linux kernel-based systems utilizing Bluetooth functionality, particularly those with customized firmware or modified drivers. Defenders should prioritize verifying the Linux kernel version and applying patches to address this vulnerability.

Defensive priority

Defenders should prioritize verifying the Linux kernel version and applying patches to address this vulnerability, particularly for systems utilizing Bluetooth functionality.

Recommended defensive actions

• Verify Linux kernel version and apply patches
• Review system configurations for Bluetooth functionality
• Monitor system logs for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and associated references provide details on the vulnerability, including its description and potential impact. However, the record does not provide explicit information on exploitation or affected systems.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.