CVE-2026-74507: Bluetooth: HIDP: validate numbered report payloads
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 on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 011bf4350d941f1995b2bd4b815ee206cacf2b8e, 27cc0e603355c585f1e5da8398faa4d36d498188, 34f53d27b81a16a02828c8fdfa4e02badc326f17; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 011bf4350d941f1995b2bd4b815ee206cacf2b8e, 27cc0e603355c585f1e5da8398faa4d36d498188, 34f53d27b81a16a02828c8fdfa4e02badc326f17; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 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: HIDP: validate numbered report payloads When hidp_get_raw_report() waits for a numbered report, hidp_process_data() compares the expected report number with skb->data[0]. A connected HIDP peer can reply with only a DATA transaction header, leaving the skb empty after the header is removed. KMSAN reports an uninitialized-value use in hidp_session_run(), with the value originating in __alloc_skb() through vhci_write(). The transaction header checks remove the empty-frame reports, but this report remains until the payload check is added. The comparison can also consume a peer-controlled byte beyond the declared L2CAP PDU. A DATA | FEATURE response followed by an extra 0x01 byte made the current code accept that byte as report ID 1 and complete HIDIOCGFEATURE with a zero-byte result. With this change the malformed response is rejected with -EIO, while a subsequent valid response still succeeds. Require a payload byte before comparing a numbered report ID. Unnumbered reports continue to accept an empty payload.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
Report tools
Action score
28
Monitor
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.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 2.6.39affected
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before 011bf4350d941f1995b2bd4b815ee206cacf2b8eaffected · git
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before 689d8bb7fee96b7196b572b015b6055c6616ce0caffected · git
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before c73beb320f5705e508bf7d385b8cc5ef8d9c8b69affected · git
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before b7ad105d46acd828e424454815e4cd31069e047aaffected · git
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before 7e7162427659b70ea17cd41b1f79e2e64c246690affected · git
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before 27cc0e603355c585f1e5da8398faa4d36d498188affected · git
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before 9c841f59e10b5d75c398a3fc6b2da448d2a2276baffected · git
- 0ff1731a1ae51e8e48cd559d70db536281c47f8e and later · before 34f53d27b81a16a02828c8fdfa4e02badc326f17affected · git
- before 2.6.39not affected · semver
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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74505Aug 15, 2026 · ALSA: 6fire: Fix UAF at error handling during probe0Monitor
- ← EarlierCVE-2026-74506Aug 15, 2026 · afs: Fix UAF when sending a message31Monitor
- Later →CVE-2026-74508Aug 15, 2026 · Bluetooth: HIDP: reject frames without a transaction header35Monitor
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 | 011bf4350d941f1995b2bd4b815ee206cacf2b8e | Vendor (CNA) |
| Linux Linux | 27cc0e603355c585f1e5da8398faa4d36d498188 | Vendor (CNA) |
| Linux Linux | 34f53d27b81a16a02828c8fdfa4e02badc326f17 | Vendor (CNA) |
| Linux Linux | 689d8bb7fee96b7196b572b015b6055c6616ce0c | Vendor (CNA) |
| Linux Linux | 7e7162427659b70ea17cd41b1f79e2e64c246690 | Vendor (CNA) |
| Linux Linux | 9c841f59e10b5d75c398a3fc6b2da448d2a2276b | Vendor (CNA) |
| Linux Linux | b7ad105d46acd828e424454815e4cd31069e047a | Vendor (CNA) |
| Linux Linux | c73beb320f5705e508bf7d385b8cc5ef8d9c8b69 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
nvd-secondary
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/27cc0e603355c585f1e5da8398faa4d36d498188
- git.kernel.org/stable/c/34f53d27b81a16a02828c8fdfa4e02badc326f17
- git.kernel.org/stable/c/689d8bb7fee96b7196b572b015b6055c6616ce0c
- git.kernel.org/stable/c/7e7162427659b70ea17cd41b1f79e2e64c246690
- git.kernel.org/stable/c/9c841f59e10b5d75c398a3fc6b2da448d2a2276b
- git.kernel.org/stable/c/b7ad105d46acd828e424454815e4cd31069e047a
- git.kernel.org/stable/c/c73beb320f5705e508bf7d385b8cc5ef8d9c8b69
Vendor advisories and official records. Exploit/PoC links are deliberately left out.