CVE-2026-74507

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

Bluetooth: HIDP: validate numbered report payloads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b7ad105d46acd828e424454815e4cd31069e047a
generic

Bluetooth: HIDP: validate numbered report payloads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c841f59e10b5d75c398a3fc6b2da448d2a2276b
generic

Bluetooth: HIDP: validate numbered report payloads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e7162427659b70ea17cd41b1f79e2e64c246690
generic

Bluetooth: HIDP: validate numbered report payloads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34f53d27b81a16a02828c8fdfa4e02badc326f17
generic

Bluetooth: HIDP: validate numbered report payloads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27cc0e603355c585f1e5da8398faa4d36d498188

Vendor Advisories for CVE-2026-74507(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 04:29 UTCEG score recompute
  2. 2026-08-21 04:29 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:52 UTCGHSA enrichment
  5. 2026-08-20 05:15 UTCGHSA enrichment
  6. 2026-08-19 17:38 UTCEG score recompute
  7. 2026-08-19 17:38 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:53 UTCEG score recompute
  10. 2026-08-19 16:53 UTCGHSA enrichment
  11. 2026-08-19 05:47 UTCGHSA enrichment
  12. 2026-08-18 18:10 UTCEG score recompute
  13. 2026-08-18 18:09 UTCGHSA enrichment
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 06:31 UTCGHSA enrichment
  17. 2026-08-17 18:54 UTCEG score recompute
  18. 2026-08-17 18:54 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 06:24 UTCEG score recompute
  21. 2026-08-17 06:24 UTCGHSA enrichment
  22. 2026-08-17 05:55 UTCEG score recompute▲ 7.10
  23. 2026-08-17 05:55 UTCGHSA enrichment
  24. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  25. 2026-08-17 05:39 UTCEG score recompute
Show 7 more
  1. 2026-08-17 05:39 UTCGHSA enrichment
  2. 2026-08-17 05:39 UTCMITRE cvelistV5
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-15 13:27 UTCNVD update
  6. 2026-08-15 12:39 UTCEG score recompute
  7. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74507?
CVE-2026-74507 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HIDP: validate numbered report payloads When hidpgetraw_report() waits for a numbered report, hidpprocessdata() compares the expected report number with skb->data[0]. A connected HIDP peer can reply with only a DATA…
When was CVE-2026-74507 disclosed?
CVE-2026-74507 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74507 actively exploited?
CVE-2026-74507 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.3% of all scored CVEs.
What is the CVSS score of CVE-2026-74507?
CVE-2026-74507 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-74507?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74507, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74507

Explore →

Is Your Infrastructure Affected by CVE-2026-74507?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs