CVE-2026-74507 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Bluetooth HIDP implementation users and deployers, Linux distribution maintainers, and security teams responsible for Linux kernel vulnerability management.

Why it matters

A vulnerability in the Linux kernel's Bluetooth HIDP implementation could allow an attacker to trigger an uninitialized-value use or consume a peer-controlled byte beyond the declared L2CAP PDU. Defenders should verify and apply patches, monitor for exploitation attempts, and review Linux kernel versions and configurations for exposure.

• Verify and apply patches to prevent potential crashes or information disclosure
• Monitor for potential exploitation attempts targeting this vulnerability
• Review Linux kernel versions and configurations for exposure

Technical summary

The Linux kernel's Bluetooth HIDP implementation did not properly validate numbered report payloads, allowing for an uninitialized-value use in hidp_session_run(). A connected HIDP peer could reply with only a DATA transaction header, leaving the skb empty after the header is removed. This could lead to the consumption of a peer-controlled byte beyond the declared L2CAP PDU. The issue has been resolved by requiring a payload byte before comparing a numbered report ID.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the patch to the Linux kernel's Bluetooth HIDP implementation
• Verify that the Linux kernel version is up-to-date and not vulnerable
• Monitor for potential exploitation attempts targeting this vulnerability
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to source code changes. Linux kernel developers and maintainers should verify and apply patches, monitor for exploitation attempts, and review Linux kernel versions and configurations for exposure. The vulnerability could allow an attacker to trigger an uninitialized-value use or consume a peer-controlled byte beyond the declared L2CAP PDU. Defenders should focus on validating and applying patches, ensuring

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.