CVE-2026-74461: i2c: imx: Cancel hrtimer before clearing slave pointer
Noroxi assessment
Priority: Monitor (action score 33/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.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 470fe15fb3bb2eba6629be301ca7e991ee3cfb7e, 6ac7702b6cc2b94aaed9ef2d95bfbefcdc90061f, 753060f2b77ff2f386addbd3ecadb95b9f90cddd; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 470fe15fb3bb2eba6629be301ca7e991ee3cfb7e, 6ac7702b6cc2b94aaed9ef2d95bfbefcdc90061f, 753060f2b77ff2f386addbd3ecadb95b9f90cddd; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.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: i2c: imx: Cancel hrtimer before clearing slave pointer In i2c_imx_unreg_slave(), the slave pointer is set to NULL after disabling interrupts. However, a pending interrupt might already have started the hrtimer (i2c_imx_slave_timeout) before the pointer was cleared. If the hrtimer fires after i2c_imx->slave is set to NULL, the timer callback i2c_imx_slave_finish_op() will call i2c_imx_slave_event() with a NULL slave pointer, which results in a use-after-free / NULL pointer dereference. Fix by canceling the hrtimer and waiting for it to complete after disabling interrupts, before clearing the slave pointer.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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
- 5.11affected
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before e3da77bdb4015051656bb472c295656bbea03b6faffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before 470fe15fb3bb2eba6629be301ca7e991ee3cfb7eaffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before a8a1f9ac3d763e721586f15479ef9140b216ddf3affected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before 753060f2b77ff2f386addbd3ecadb95b9f90cdddaffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before affd62f5719a78135b7441aa49c8cab3c3b5e838affected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before dab4762ee7f3fd0a01980d5407ba48d0261d3bffaffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before 6ac7702b6cc2b94aaed9ef2d95bfbefcdc90061faffected · git
- before 5.11not affected · semver
- 5.15.216 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74458Aug 15, 2026 · can: kvaser_usb_leaf: kvaser_usb_leaf_wait_cmd(): validate received command extents0Monitor
- ← EarlierCVE-2026-74460Aug 15, 2026 · can: ems_usb: validate CPC message lengths0Monitor
- Later →CVE-2026-74464Aug 15, 2026 · net: openvswitch: fix skb leak on flow key update failure during ct0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 470fe15fb3bb2eba6629be301ca7e991ee3cfb7e | Vendor (CNA) |
| Linux Linux | 6ac7702b6cc2b94aaed9ef2d95bfbefcdc90061f | Vendor (CNA) |
| Linux Linux | 753060f2b77ff2f386addbd3ecadb95b9f90cddd | Vendor (CNA) |
| Linux Linux | a8a1f9ac3d763e721586f15479ef9140b216ddf3 | Vendor (CNA) |
| Linux Linux | affd62f5719a78135b7441aa49c8cab3c3b5e838 | Vendor (CNA) |
| Linux Linux | dab4762ee7f3fd0a01980d5407ba48d0261d3bff | Vendor (CNA) |
| Linux Linux | e3da77bdb4015051656bb472c295656bbea03b6f | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package 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.
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/6ac7702b6cc2b94aaed9ef2d95bfbefcdc90061f
- git.kernel.org/stable/c/753060f2b77ff2f386addbd3ecadb95b9f90cddd
- git.kernel.org/stable/c/a8a1f9ac3d763e721586f15479ef9140b216ddf3
- git.kernel.org/stable/c/affd62f5719a78135b7441aa49c8cab3c3b5e838
- git.kernel.org/stable/c/dab4762ee7f3fd0a01980d5407ba48d0261d3bff
- git.kernel.org/stable/c/e3da77bdb4015051656bb472c295656bbea03b6f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.