What is CVE-2026-74507?

CVE-2026-74507 is a High severity Linux kernel vulnerability with a CVSS score of 7.1 out of 10, affecting Linux kernel versions from 2.6.39 onward and patched in 5.10.265, 5.15.216, 6.1.183 and others. CVE-2026-74507 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-74507?

CVE-2026-74507 has a CVSS score of 7.1 out of 10, rated High severity. The vector string is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N.

Is there a patch available for CVE-2026-74507?

Yes, CVE-2026-74507 has been patched. Fixed versions include 5.10.265, 5.15.216, 6.1.183 and others. If you are running Linux kernel 2.6.39 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-74507 actively exploited?

CVE-2026-74507 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-74507

High

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.

Package Linux Kernel

Published 2026-08-15

Last modified 2026-08-19

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.1

out of 10

High

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Vector string

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

Affected versions

Linux kernel versions 2.6.39 and later are affected. Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2 and their respective stable series.

Affected from

≥ 2.6.39

Fixed in

✓ 5.10.265 5.10.x ✓ 5.15.216 5.15.x ✓ 6.1.183 6.1.x ✓ 6.6.151 6.6.x ✓ 6.12.103 6.12.x ✓ 6.18.44 6.18.x ✓ 7.1.8 7.1.x ✓ 7.2

References

8 total

Showing 5 of 8 references View all on NVD

Details

CVE ID CVE-2026-74507

Severity High

CVSS score 7.1 / 10

CVSS version 3.1

Published 2026-08-15

Modified 2026-08-19

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-74507?

CVE-2026-74507 is a High severity Linux kernel vulnerability with a CVSS score of 7.1 out of 10 . It affects Linux kernel versions from 2.6.39 onward and has been patched in 5.10.265, 5.15.216, 6.1.183 and others. CVE-2026-74507 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-74507?

CVE-2026-74507 has a CVSS score of 7.1 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N.
Is there a patch available for CVE-2026-74507?

Yes. CVE-2026-74507 has been patched. Fixed versions include 5.10.265, 5.15.216, 6.1.183 and others. If you are running Linux kernel 2.6.39 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-74507 actively exploited?

No. CVE-2026-74507 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.