CVE-2026-80767
Description
A flaw was found in the Linux kernel's Human Interface Device (HID) sensor custom driver. A use-after-free vulnerability exists where the enable_sensor sysfs attribute can be accessed either before its associated memory is properly initialized or after it has been freed during device removal. A local attacker could exploit this condition to cause a system crash (denial of service) or potentially achieve arbitrary code execution due to memory corruption.
Statement
HID sensor custom exposes an enable_sensor sysfs attribute that can call set_power_report_state and dereference sensor_inst power_state and report_state. These pointers refer to entries in sensor_inst fields, so accessing enable_sensor before field state is initialized or while field attributes are being removed can lead to a use-after-free. A local attacker with access to the sysfs attribute could try to race probe or remove paths and trigger a kernel crash. For the CVSS the PR:L is used for the paranoid score because some deployments may delegate sensor sysfs access to non-root users or service accounts even though default sysfs writes are often administrator controlled. The issue is not network reachable. Impact is at least local denial of service and in worst case may allow confidentiality or integrity impact due to kernel UAF memory corruption, so it should be reviewed manually.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
