CVE-2026-74302 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems should assess exposure and apply patches or mitigations as needed. Additionally, security teams and vulnerability management teams should review the vulnerability and its potential impact on their systems.

Why it matters

This vulnerability could potentially allow a local attacker to execute arbitrary code or cause a denial-of-service condition in Linux-based systems. Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems should assess exposure and apply patches or mitigations as needed.

• Potential code execution or denial-of-service
• Requires verification of affected versions and patch application
• Monitoring system logs for suspicious activity is recommended

Technical summary

The `hci_unregister_dev()` function in the Linux kernel's Bluetooth subsystem does not properly disable timers before freeing the `hci_dev` structure. This can lead to a use-after-free vulnerability if a timeout fires during device teardown. The vulnerability could potentially allow a local attacker to execute arbitrary code or cause a denial-of-service condition in Linux-based systems. Linux kernel developers and maintainers should assess exposure and apply patches or mitigations as needed to prevent potential exploitation.

Defensive priority

High

Recommended defensive actions

• Review and apply patches from the Linux kernel maintainers
• Disable Bluetooth if not required
• Monitor system logs for suspicious activity
• Verify affected versions and apply patches or mitigations as needed
• Review compensating controls for exposed systems while remediation is scheduled and verified
• 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

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description and affected versions. However, there is limited information about potential exploits or attacks. The vulnerability was introduced due to improper handling of timers in the `hci_unregister_dev()` function. Defenders should verify affected versions, review patches, and monitor system logs for suspicious activity.

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.