Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 244a1cb638370490ed74a8adb5cc3f1212602e32, 2ce90cfc6646a32100feabd7110ae0352aa01167, 7bb79a3cf45e0805aef74457e19deb77e18cf196; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 244a1cb638370490ed74a8adb5cc3f1212602e32, 2ce90cfc6646a32100feabd7110ae0352aa01167, 7bb79a3cf45e0805aef74457e19deb77e18cf196; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80767

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.1affected
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before c2be74b0272b7f8f60739e7aaf0d36c0befe7136affected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855affected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before d37ff4e3635c18af907f25712596f8ccec323751affected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 2ce90cfc6646a32100feabd7110ae0352aa01167affected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 244a1cb638370490ed74a8adb5cc3f1212602e32affected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 8406d4b69d48bc72fb6f8812a65a17a1f903440baffected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before c0757f10610542d763bd0bf9bda455b78afeef0baffected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 7bb79a3cf45e0805aef74457e19deb77e18cf196affected · git
    • 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before ad8fb82b04422f49530d2aa2753cc81d1c60102caffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.107-16.12.107-1
Debian:14linuxbefore 7.1.12-17.1.12-1
openSUSE:Tumbleweedkernel-sourcebefore 7.2.5-1.17.2.5-1.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80765Sep 4, 2026 · HID: hyperv: validate initial device info bounds
    0Monitor
  • ← EarlierCVE-2026-80766Sep 4, 2026 · HID: uclogic: fix use-after-free of inrange_timer on remove
    0Monitor
  • Later →CVE-2026-80768Sep 4, 2026 · HID: ft260: fix stack-use-after-return write in I2C read race
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux244a1cb638370490ed74a8adb5cc3f1212602e32Vendor (CNA)
Linux Linux2ce90cfc6646a32100feabd7110ae0352aa01167Vendor (CNA)
Linux Linux7bb79a3cf45e0805aef74457e19deb77e18cf196Vendor (CNA)
Linux Linux8406d4b69d48bc72fb6f8812a65a17a1f903440bVendor (CNA)
Linux Linuxad8fb82b04422f49530d2aa2753cc81d1c60102cVendor (CNA)
Linux Linuxc0757f10610542d763bd0bf9bda455b78afeef0bVendor (CNA)
Linux Linuxc2be74b0272b7f8f60739e7aaf0d36c0befe7136Vendor (CNA)
Linux Linuxd37ff4e3635c18af907f25712596f8ccec323751Vendor (CNA)
Linux Linuxd7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.2.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records