NVD / CVE Program· CNA Linux

CVE-2026-64363: HID: appleir: fix UAF on pending key_up_timer in remove()

Noroxi assessment

Priority: Monitor (action score 31/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.16% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 05e3decc55d1deca9410e0eb36466651fcbe57a5, 3755f6e25776b8b12ddf062f9b573f05090e4034, 37a52c61d4f78153c38ae1f7491dfcc8ac828dcf; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 05e3decc55d1deca9410e0eb36466651fcbe57a5, 3755f6e25776b8b12ddf062f9b573f05090e4034, 37a52c61d4f78153c38ae1f7491dfcc8ac828dcf; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-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: appleir: fix UAF on pending key_up_timer in remove() appleir_remove() runs hid_hw_stop() before timer_delete_sync(). hid_hw_stop() synchronously unregisters the HID input device via hid_disconnect() -> hidinput_disconnect() -> input_unregister_device(), which drops the last reference and frees the underlying input_dev when no userspace handle holds it open. key_up_tick() reads appleir->input_dev and calls input_report_key() / input_sync() on it. The timer is armed from appleir_raw_event() with a HZ/8 (~125 ms) timeout on every keydown and key-repeat report. If a key was pressed shortly before the device is disconnected, the timer can fire after hid_hw_stop() has freed input_dev but before the teardown drains it. A simple reorder is not sufficient. Putting the timer drain first still leaves a window where a USB URB completion (raw_event) running during hid_hw_stop() can call mod_timer() and re-arm the timer, which then fires after hidinput_disconnect() has freed input_dev. The same URB-completion window also lets raw_event() reach key_up(), key_down() and battery_flat() directly, all of which dereference appleir->input_dev. Introduce a 'removing' flag on struct appleir, gated by the existing spinlock. appleir_remove() sets the flag under the lock and then shuts down the timer with timer_shutdown_sync(), which both drains any in-flight callback and permanently disables further mod_timer() calls. appleir_raw_event() and key_up_tick() bail out early if the flag is set, so no path can arm or run the timer, or dereference appleir->input_dev, after remove() has started tearing down. The keyrepeat and flatbattery branches of appleir_raw_event() previously called into the input layer without holding the spinlock; take it now so the flag check is well-defined. This incidentally closes a pre-existing read-side race on appleir->current_key in the keyrepeat branch. This bug is structurally a sibling of commit 4db2af929279 ("HID: appletb-kbd: fix UAF in inactivity-timer cleanup path") and has been present since the driver was introduced.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Jul 25, 2026
Updated: Nov 6, 2026
EPSS: 0.1% · 6th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

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

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel3.10 and later · before 5.10.261
linux linux kernel5.11 and later · before 5.15.212
linux linux kernel5.16 and later · before 6.1.178
linux linux kernel6.2 and later · before 6.6.145
linux linux kernel6.7 and later · before 6.12.97
linux linux kernel6.13 and later · before 6.18.39
linux linux kernel6.19 and later · before 7.1.4
linux linux kernel7.2

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
- 3.10affected
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before 89ef67359672bf4cd6921524e39f61648fe38c0faffected · git
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before 3d30a0bb0e79621ae921b487835c56198adfafa3affected · git
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before 37a52c61d4f78153c38ae1f7491dfcc8ac828dcfaffected · git
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before 05e3decc55d1deca9410e0eb36466651fcbe57a5affected · git
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before 3755f6e25776b8b12ddf062f9b573f05090e4034affected · git
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before b363d964ca829c1761c9f04188dfa28f90b0f2d4affected · git
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before 6b0838e86da88b1d3bff86f19761ff25af73eacaaffected · git
- 9a4a5574ce427c364d81746fc7fb82d86b5f1a7e and later · before 75fe87e19d8aff81eb2c64d15d244ab8da4de945affected · git
- before 3.10not 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.180-1	6.1.180-1
Debian:12	linux-6.12	before 6.12.100-1~deb12u1	6.12.100-1~deb12u1
Debian:13	linux	before 6.12.100-1	6.12.100-1
Debian:14	linux	before 7.1.4-1	7.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-64357Jul 25, 2026 · xfs: fix exchmaps reservation limit check
22Monitor
← EarlierCVE-2026-64362Jul 25, 2026 · HID: lg-g15: cancel pending work on remove to fix a use-after-free
31Monitor
Later →CVE-2026-64364Jul 25, 2026 · HID: multitouch: fix out-of-bounds bit access on mt_io_flags
35Monitor

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	05e3decc55d1deca9410e0eb36466651fcbe57a5	Vendor (CNA)
Linux Linux	3755f6e25776b8b12ddf062f9b573f05090e4034	Vendor (CNA)
Linux Linux	37a52c61d4f78153c38ae1f7491dfcc8ac828dcf	Vendor (CNA)
Linux Linux	3d30a0bb0e79621ae921b487835c56198adfafa3	Vendor (CNA)
Linux Linux	6b0838e86da88b1d3bff86f19761ff25af73eaca	Vendor (CNA)
Linux Linux	75fe87e19d8aff81eb2c64d15d244ab8da4de945	Vendor (CNA)
Linux Linux	89ef67359672bf4cd6921524e39f61648fe38c0f	Vendor (CNA)
Linux Linux	b363d964ca829c1761c9f04188dfa28f90b0f2d4	Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.0	6.6.145.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.180-1 · Debian:12	Package registry (OSV)
debian:linux-6.12	6.12.100-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.

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

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
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: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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— → noneNov 6, 2026, 6:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

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

References

git.kernel.org/stable/c/05e3decc55d1deca9410e0eb36466651fcbe57a5

Show all references (7 more)

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

All records