CVE-2026-97907: Linux kernel · Bluetooth: btrtl: Don't leak return code when parsing firmware format v2
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c4249cf6e80b1bd62a6a409aaabe760fe025dac3 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c4249cf6e80b1bd62a6a409aaabe760fe025dac3, ba96047bba4a6101267cf4f6b3057cbc58e6c554, 422f6547259654bae690713614c794dd1e2c0a0b +2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel source code as indicated by the fixed commit versions. Users and administrators should update to the fixed Linux kernel versions containing the patches referenced by the commit hashes to remediate this issue.
Description
A vulnerability in the Linux kernel Bluetooth subsystem (btrtl) involves leaking an uninitialized return code when parsing firmware format version 2. This occurs when the key_id from the chip is zero, causing the function rtlbt_parse_firmware_v2() to improperly handle security headers and leak return codes from previous sections. The issue has been fixed by correcting the loop control flow to properly skip sections and improve code readability.
References
- git.kernel.org/stable/c/ba96047bba4a6101267cf4f6b3057cbc58e6c554 (opens in a new tab)
- git.kernel.org/stable/c/90f3a142b5f8596a565b8e080d18a8050be6edef (opens in a new tab)
- git.kernel.org/stable/c/422f6547259654bae690713614c794dd1e2c0a0b (opens in a new tab)
- git.kernel.org/stable/c/c4249cf6e80b1bd62a6a409aaabe760fe025dac3 (opens in a new tab)
- git.kernel.org/stable/c/83e3e515fd261600ed8491fb0a8bcdfb115c904e (opens in a new tab)