VulnerabilityPublished 22 Apr 2026Updated 5 Nov 2026

CVE-2026-31522: Linux kernel · HID: magicmouse: avoid memory leak in magicmouse_report_fixup()

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in fa95b0146358b49f9858139b67314591fd5871b0 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 22:17 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in fa95b0146358b49f9858139b67314591fd5871b0, d84c21aabaab517b9aaf9bc1d785922cb9db2f31, 579c4c9857acdc8380fa99803f355f878bd766cb +6

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=5.15.17 <5.15.203 >=5.16.3 <5.17	Fixed in fa95b0146358b49f9858139b67314591fd5871b0 d84c21aabaab517b9aaf9bc1d785922cb9db2f31 579c4c9857acdc8380fa99803f355f878bd766cb 136f605e246b4bfe7ac2259471d1ff814aed0084 91e8c6e601bdc1ccdf886479b6513c01c7e51c2c 79e5dcc95d9abed6f8203cfd529f4ec71f0e505d 7edfe4346b052b708645d0acc0f186425766b785 5.17 5.15.203
LinuxLinux	Affected =5.17	Fixed in–

AI-suggested

The vulnerability has been fixed in Linux kernel versions 5.15.203, 5.17, and related commits. Users and administrators should update to these or later kernel versions to remediate the issue. No additional mitigation actions are required beyond applying the official fixes.

Description

A memory leak vulnerability was identified and resolved in the Linux kernel's magicmouse_report_fixup() function. The function returned a newly allocated buffer without freeing it, leading to potential memory exhaustion over time. The issue affects specific Linux kernel versions prior to the fixes. The vulnerability does not have known exploits in the wild and has been addressed in several fixed versions.

Impact

The vulnerability causes a memory leak in the Linux kernel when handling Magic Mouse input reports. Over time, this could lead to increased memory consumption and potential system instability or degraded performance. There are no reports of exploitation in the wild.

Summary

The Linux kernel's magicmouse_report_fixup() function improperly handled memory by returning a kmemdup()-allocated buffer without freeing it, causing a memory leak. The caller does not take ownership of the returned pointer, which violates expected memory management practices. This flaw was fixed in Linux kernel versions 5.15.203, 5.17, and related commits, preventing the leak by correcting the function's behavior.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 22:17 UTC

Technical details

References

Community reviews

Related threats