CVE Intelligence
Unknown

CVE-2026-80767 — HID: sensor: custom: Fix use-after-free in enable_sensor

In the Linux kernel, the following vulnerability has been resolved: HID: sensor: custom: Fix use-after-free in enable_sensor enable_sensor_store() can call set_power_report_state(), which dereferences sensor_inst->power_state and sensor_inst->report_state. These pointers refer to entries in sensor_inst->fields. Create the field attributes before exposing the enable_sensor sysfs attribute, so enable_sensor cannot be accessed before the state it depends on has been initialized. On remove, delete enable_sensor before freeing the field attributes, so a concurrent sysfs write cannot dereference freed memory through power_state or report_state.

Published Sep 4, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.2%
ahead of 9% of scored CVEs · Oct 26, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < c2be74b0272b7f8f60739e7aaf0d36c0befe7136≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < d37ff4e3635c18af907f25712596f8ccec323751≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < 2ce90cfc6646a32100feabd7110ae0352aa01167≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < 244a1cb638370490ed74a8adb5cc3f1212602e32≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < 8406d4b69d48bc72fb6f8812a65a17a1f903440b≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < c0757f10610542d763bd0bf9bda455b78afeef0b≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < 7bb79a3cf45e0805aef74457e19deb77e18cf196
and 2 more ≥ 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and < ad8fb82b04422f49530d2aa2753cc81d1c60102cversion 4.1
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.20%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 4, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

11 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 14h
  • CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 14h
  • CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 14h
  • CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 14h
  • CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 14h
  • CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 14h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80767 is "HID: sensor: custom: Fix use-after-free in enable_sensor", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.