GHSA-CC6Q-P4XG-QP8M
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In 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'src'.
Fix it by really skipping a loop with `continue'. For consistency and readability, also do the same for the default case.
{
"affected": [],
"aliases": [
"CVE-2026-97907"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:17Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btrtl: Don\u0027t leak return code when parsing firmware format v2\n\nWhen key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally\nignores all security headers. However, the implementation simply breaks\nfrom a switch statement and leaks uninitialized return code `rc\u0027 (if the\nfirst section is a security one) or the previous section\u0027s `rc\u0027.\n\nFix it by really skipping a loop with `continue\u0027. For consistency and\nreadability, also do the same for the default case.",
"id": "GHSA-cc6q-p4xg-qp8m",
"modified": "2026-09-25T12:31:28Z",
"published": "2026-09-25T12:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97907"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/422f6547259654bae690713614c794dd1e2c0a0b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/83e3e515fd261600ed8491fb0a8bcdfb115c904e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/90f3a142b5f8596a565b8e080d18a8050be6edef"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c4249cf6e80b1bd62a6a409aaabe760fe025dac3"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.