CVE-2026-31408: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold
Published Apr 6, 2026
·Updated
Bluetooth: SCO: Fix use-after-free in scorecvframe() due to missing sockhold
Affected Software
18 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.130.1-3
Linux Linux kernel>=2.6.12.1<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=2.6.12
Linux Linux kernel=2.6.12-rc2
Linux Linux kernel=2.6.12-rc3
Linux Linux kernel=2.6.12-rc4
Linux Linux kernel=2.6.12-rc5
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Event History
Apr 6, 2026
CVE Published
via MITRE·07:38 AM
Data Sourced
via MITRE·07:38 AM
DescriptionSeverity
Data Sourced
via NVD·08:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·09:01 AM
DescriptionSeverityAffected Software
Apr 7, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-31408?
CVE-2026-31408 is classified as a high-severity vulnerability due to the potential for remote code execution.
2
How do I fix CVE-2026-31408?
To fix CVE-2026-31408, apply the latest patches for the Linux kernel that address the use-after-free vulnerability.
3
What systems are affected by CVE-2026-31408?
CVE-2026-31408 affects all versions of the Linux kernel that implement Bluetooth SCO functionality.
4
What is the impact of CVE-2026-31408?
The impact of CVE-2026-31408 can lead to denial of service or arbitrary code execution through Bluetooth connections.
5
When was CVE-2026-31408 published?
CVE-2026-31408 was published in 2026, detailing its existence and providing a reference for remediation.