CVE-2026-31524: HID: asus: avoid memory leak in asus_report_fixup()

Published Apr 22, 2026
·
Updated

HID: asus: avoid memory leak in asusreportfixup()

Affected Software

12 affected componentsFixes available
Linux Linux kernel (HID: asus)
Linux Linux kernel>=4.14<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Microsoft azl3 kernel 6.6.130.1-3
Microsoft azl3 kernel 6.6.130.1-3<6.6.134.1-2
6.6.134.1-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.134.1-2
  2. Compensating control

    In the Linux kernel HID ASUS driver, update asus_report_fixup() to use devm_kzalloc() so allocated memory is freed automatically when the device is removed, and copy only the original descriptor size to avoid the out-of-bounds read.

Event History

Apr 22, 2026
CVE Published
via MITRE·01:54 PM
Data Sourced
via MITRE·01:54 PM
Description
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-31524?

CVE-2026-31524 is classified as a medium severity vulnerability due to its potential to cause a memory leak in the Linux kernel.

2

How do I fix CVE-2026-31524?

To fix CVE-2026-31524, you should apply the latest patch from the Linux kernel maintainers that addresses the memory leak in the asus_report_fixup() function.

3

What systems are affected by CVE-2026-31524?

CVE-2026-31524 affects the Linux kernel specifically in the HID: asus module.

4

What impact does CVE-2026-31524 have on my system?

The impact of CVE-2026-31524 includes potential system instability or performance degradation due to memory leaks.

5

Is there a workaround for CVE-2026-31524?

Currently, there are no known workarounds for CVE-2026-31524, so updating to the patched version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203