CVE-2026-97907

Unknown

Last modified

CVE-2026-97907 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply breaks from a switch statement and leaks uninitialized return code `rc' (if the first section is a security one) or the previous section's `rc'. Fix it by really skipping a loop with `continue'.

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply breaks from a switch statement and leaks uninitialized return code `rc' (if the first section is a security one) or the previous section's `rc'. Fix it by really skipping a loop with `continue'. For consistency and readability, also do the same for the default case.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa, < 90f3a142b5f8596a565b8e080d18a8050be6edef; >= 9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa, < 422f6547259654bae690713614c794dd1e2c0a0b; >= 9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa, < c4249cf6e80b1bd62a6a409aaabe760fe025dac3; >= 9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa, < 83e3e515fd261600ed8491fb0a8bcdfb115c904e
LinuxLinux6.4

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97907?
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply breaks from a switch statement and leaks uninitialized return code `rc' (if the first section is a security one) or the previous section's `rc'. Fix it by really skipping a loop with `continue'. For consistency and readability, also do the same for the default case.
How severe is CVE-2026-97907?
Severity scoring for CVE-2026-97907 is pending analysis.
How do I fix CVE-2026-97907?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-97907?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST