CVE-2026-74507

HIGHCVSS 7.1/10EPSS 0.23%

Last modified

CVE-2026-74507 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.23% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
7.1/10

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS Probability
0.23%

14.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

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

VendorProductVersions
LinuxLinux>= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < 011bf4350d941f1995b2bd4b815ee206cacf2b8e; >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < 689d8bb7fee96b7196b572b015b6055c6616ce0c; >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < c73beb320f5705e508bf7d385b8cc5ef8d9c8b69; >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < b7ad105d46acd828e424454815e4cd31069e047a; >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < 7e7162427659b70ea17cd41b1f79e2e64c246690; >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < 27cc0e603355c585f1e5da8398faa4d36d498188; >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < 9c841f59e10b5d75c398a3fc6b2da448d2a2276b; >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e, < 34f53d27b81a16a02828c8fdfa4e02badc326f17
LinuxLinux2.6.39

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74507?
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.
How severe is CVE-2026-74507?
CVE-2026-74507 has a CVSS score of 7.1/10 (HIGH severity). The EPSS model estimates a 0.23% probability of exploitation in the next 30 days.
How do I fix CVE-2026-74507?
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-74507?

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

Scan your code now

Source: NVD / NIST