CVE-2024-36033: Bluetooth: qca: fix info leak when fetching board id
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0adcf6be1445ed50bfd4a451a7a782568f270197, a3dff121a7f5104c4c2d47edaa2351837ef645dd, ba307abed5e09759845c735ba036f8c12f55b209.
Low priority for now. Upgrade to Linux Linux 0adcf6be1445ed50bfd4a451a7a782568f270197, a3dff121a7f5104c4c2d47edaa2351837ef645dd, ba307abed5e09759845c735ba036f8c12f55b209 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix info leak when fetching board id Add the missing sanity check when fetching the board id to avoid leaking slab data when later requesting the firmware.
- Published
- May 30, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-668
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.7affected
- c3c1bd421db6187ee455995bfbf1ba16d98f5e6b and later · before a3dff121a7f5104c4c2d47edaa2351837ef645ddaffected · git
- ad643241d455fdd2516d46cfa54bd0c5e504fc86 and later · before bcccdc947d2ca5972b1e92d0dea10803ddc08cebaffected · git
- a381ee26d7c70dbc048cd17c4e0f40619118ff1f and later · before ba307abed5e09759845c735ba036f8c12f55b209affected · git
- a7f8dedb4be2cc930a29af24427b885405ecd15d and later · before f30c37cb4549baf8377434892d520fe7769bdba7affected · git
- a7f8dedb4be2cc930a29af24427b885405ecd15d and later · before 0adcf6be1445ed50bfd4a451a7a782568f270197affected · git
- before 6.7not affected · semver
- 6.8.10 and later · up to and including 6.8.*not affected · semver
- 6.9 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.7 and later · before 6.8.10
- linux linux kernel6.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.94-1 | 6.1.94-1 |
| Debian:13 | linux | before 6.8.11-1 | 6.8.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-36031May 30, 2024 · keys: Fix overwrite of key expiration on instantiation39Monitor
- ← EarlierCVE-2024-36032May 30, 2024 · Bluetooth: qca: fix info leak when fetching fw build id28Monitor
- Later →CVE-2024-36880May 30, 2024 · Bluetooth: qca: add missing firmware sanity checks31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0adcf6be1445ed50bfd4a451a7a782568f270197 | Vendor (CNA) |
| Linux Linux | a3dff121a7f5104c4c2d47edaa2351837ef645dd | Vendor (CNA) |
| Linux Linux | ba307abed5e09759845c735ba036f8c12f55b209 | Vendor (CNA) |
| Linux Linux | bcccdc947d2ca5972b1e92d0dea10803ddc08ceb | Vendor (CNA) |
| Linux Linux | f30c37cb4549baf8377434892d520fe7769bdba7 | Vendor (CNA) |
| debian:linux | 6.1.94-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-22069321 days apartriscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler31Monitor
- CVE-2024-360320 days apartBluetooth: qca: fix info leak when fetching fw build id28Monitor
- CVE-2022-4875721 days apartnet: fix information leakage in /proc/net/ptype28Monitor
- CVE-2024-3949943 days apartvmci: prevent speculation leaks by sanitizing event in event_deliver()28Monitor
- CVE-2024-4388182 days apartwifi: ath12k: change DMA direction while mapping reinjected packets28Monitor
- CVE-2024-57838226 days aparts390/entry: Mark IRQ entries to fix stack depot warnings28Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-668 · Exposure of Resource to Wrong SphereCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.