Linux Kernel up to 7.2.0 HID Sensor Custom enable_sensor_store use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.82

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.2.0 and classified as very critical. Affected is the function enable_sensor_store of the component HID Sensor Custom. The manipulation results in use after free. This vulnerability is reported as CVE-2026-80767. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Linux Kernel up to 7.2.0. Affected is the function enable_sensor_store of the component HID Sensor Custom. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-80767 since 08/26/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 09/04/2026).

Upgrading to version 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.11, 7.2.1 or 7.3-rc1 eliminates this vulnerability. Applying the patch c2be74b0272b7f8f60739e7aaf0d36c0befe7136/d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855/d37ff4e3635c18af907f25712596f8ccec323751/2ce90cfc6646a32100feabd7110ae0352aa01167/244a1cb638370490ed74a8adb5cc3f1212602e32/8406d4b69d48bc72fb6f8812a65a17a1f903440b/c0757f10610542d763bd0bf9bda455b78afeef0b/7bb79a3cf45e0805aef74457e19deb77e18cf196/ad8fb82b04422f49530d2aa2753cc81d1c60102c is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.267/5.15.218/6.1.185/6.6.154/6.12.106/6.18.47/7.1.11/7.2.1/7.3-rc1
Patch: c2be74b0272b7f8f60739e7aaf0d36c0befe7136/d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855/d37ff4e3635c18af907f25712596f8ccec323751/2ce90cfc6646a32100feabd7110ae0352aa01167/244a1cb638370490ed74a8adb5cc3f1212602e32/8406d4b69d48bc72fb6f8812a65a17a1f903440b/c0757f10610542d763bd0bf9bda455b78afeef0b/7bb79a3cf45e0805aef74457e19deb77e18cf196/ad8fb82b04422f49530d2aa2753cc81d1c60102c

Timelineinfo

08/26/2026 CVE reserved
09/04/2026 +9 days Advisory disclosed
09/04/2026 +0 days VulDB entry created
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80767 (🔒)
GCVE (CVE): GCVE-0-2026-80767
GCVE (VulDB): GCVE-100-398892

Entryinfo

Created: 09/04/2026 18:00
Changes: 09/04/2026 18:00 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!