Skip to main content
VulnerabilityPublished Updated

CVE-2026-72352: Linux kernel · HID: bpf: Fix hid_bpf_get_data() range check

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in f72176bde0cc0e709e41ab170c71e8f229232af6 : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f72176bde0cc0e709e41ab170c71e8f229232af6, f81bc5a709dcbaf2a3bbef4ca7167f93900cc39f, ca373549140dfb386aa2de38364b58441b1f4885 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 658ee5a64fcfbbf758447fa3af425729eaabb0dc, < f72176bde0cc0e709e41ab170c71e8f229232af6
Fixed in
  • f72176bde0cc0e709e41ab170c71e8f229232af6
LinuxLinuxAffected
  • ≥ 658ee5a64fcfbbf758447fa3af425729eaabb0dc, < f81bc5a709dcbaf2a3bbef4ca7167f93900cc39f
Fixed in
  • f81bc5a709dcbaf2a3bbef4ca7167f93900cc39f
LinuxLinuxAffected
  • ≥ 658ee5a64fcfbbf758447fa3af425729eaabb0dc, < ca373549140dfb386aa2de38364b58441b1f4885
Fixed in
  • ca373549140dfb386aa2de38364b58441b1f4885
LinuxLinuxAffected
  • ≥ 658ee5a64fcfbbf758447fa3af425729eaabb0dc, < 61a959b82f1aecd6d2d35c208013dd077cac9d10
Fixed in
  • 61a959b82f1aecd6d2d35c208013dd077cac9d10
LinuxLinuxAffected
  • ≥ 658ee5a64fcfbbf758447fa3af425729eaabb0dc, < 2d044049421dd48212b28646a850749d4a2d57fa
Fixed in
  • 2d044049421dd48212b28646a850749d4a2d57fa
LinuxLinuxAffected
  • =6.3
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: HID: bpf: Fix hid_bpf_get_data() range check hid_bpf_get_data() returns a pointer into the HID-BPF context data when the caller-provided offset and size fit inside ctx->allocated_size. The current check adds rdwr_buf_size and offset before comparing the result against ctx->allocated_size. Since both values are unsigned, a very large size can wrap the sum below ctx->allocated_size and make the helper return a pointer even though the requested range is not contained in the backing buffer. Use check_add_overflow() to reject wrapped range ends before comparing the requested range end against ctx->allocated_size.

References

Community reviews

Loading reviews…