Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98656: iio: trigger: cancel reenable_work before freeing trigger

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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 2a57b9246cecd5dd797a42eb310d6c8816f26d9e, 4e790a5bd4249877bcf0c94db12ac490965f9296, 5.15.224; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.

Low priority for now. Upgrade to Linux Linux 2a57b9246cecd5dd797a42eb310d6c8816f26d9e, 4e790a5bd4249877bcf0c94db12ac490965f9296, 5.15.224; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.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: iio: trigger: cancel reenable_work before freeing trigger iio_trigger_notify_done_atomic() defers ->reenable() into trig->reenable_work on the system workqueue, and the worker dereferences the owning trigger through container_of(). Nothing cancels this work before iio_trig_release() frees the trigger, so a worker armed by the last in-flight IRQ can outlive the free and touch freed memory. Cancel it at the top of iio_trig_release(), which every free path reaches through the device core's final put_device(). Found by an in-house static analysis tool.

—No exploit Fix available
Published
Oct 18, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 6th 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-98656

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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

Running WordPress? Scan your site free with WP Lens

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

    • 2c5c948451d57596640b20887b06b523d376eb24, 5.17affected
    • a18aeac73c0f692ba40964f5f56e182312ae843b and later · before beec4c9e23b8293c41d3448f9807c28fc9a599d4affected · git
    • 9020ef659885f2622cfb386cc229b6d618362895 and later · before 4e790a5bd4249877bcf0c94db12ac490965f9296affected · git
    • 9020ef659885f2622cfb386cc229b6d618362895 and later · before ac5d26a46c90ff61fd574eff4e8f0d71c905828aaffected · git
    • 9020ef659885f2622cfb386cc229b6d618362895 and later · before cf513df1a2c75566cdc802d9da47f62e8d6cfd18affected · git
    • 9020ef659885f2622cfb386cc229b6d618362895 and later · before e64703280ce7a23a43c27efebeb7da457c88bf5caffected · git
    • 9020ef659885f2622cfb386cc229b6d618362895 and later · before 882d0011c59ff8ac15188ec9ce071399ecfa10adaffected · git
    • 9020ef659885f2622cfb386cc229b6d618362895 and later · before 2a57b9246cecd5dd797a42eb310d6c8816f26d9eaffected · git
    • 5.15.17 and later · before 5.15.224affected · semver
    • 5.16.3 and later · before 5.17affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.10-17.2.10-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-98653Oct 18, 2026 · KVM: s390: Fix _gaccess_shadow_fault()
    0Monitor
  • ← EarlierCVE-2026-98655Oct 18, 2026 · perf: Require kernel access for text poke events
    0Monitor
  • Later →CVE-2026-98657Oct 18, 2026 · iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure
    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 Linux2a57b9246cecd5dd797a42eb310d6c8816f26d9eVendor (CNA)
Linux Linux4e790a5bd4249877bcf0c94db12ac490965f9296Vendor (CNA)
Linux Linux5.15.224Vendor (CNA)
Linux Linux5.17Vendor (CNA)
Linux Linux882d0011c59ff8ac15188ec9ce071399ecfa10adVendor (CNA)
Linux Linuxac5d26a46c90ff61fd574eff4e8f0d71c905828aVendor (CNA)
Linux Linuxbeec4c9e23b8293c41d3448f9807c28fc9a599d4Vendor (CNA)
Linux Linuxcf513df1a2c75566cdc802d9da47f62e8d6cfd18Vendor (CNA)
Linux Linuxe64703280ce7a23a43c27efebeb7da457c88bf5cVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.06.6.161.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package 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.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 7, 2026+20 d
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. Exploit maturity— → none
  2. Fix✗ → ✓

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

References

Show all references (6 more)

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

All records