CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod

Published Jan 31, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

idpf: fix memory leak of flow steer list on rmmod

The flow steering list maintains entries that are added and removed as ethtool creates and deletes flow steering rules. Module removal with active entries causes memory leak as the list is not properly cleaned up.

Prevent this by iterating through the remaining entries in the list and freeing the associated memory during module removal. Add a spinlock (flowsteerlistlock) to protect the list access from multiple threads.

Affected Software

11 affected components
Linux Linux kernel
Linux Linux kernel>=6.17.1<6.18.6
Linux Linux kernel=6.17
Linux Linux kernel=6.19-rc1
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
Linux Linux kernel=6.19-rc5
Linux Linux kernel=6.19-rc6
Linux Linux kernel=6.19-rc7
Linux Linux kernel=6.19-rc8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Protect the flow steering list with a spinlock (flow_steer_list_lock), and during module removal iterate through the remaining entries and free their associated memory.

Event History

Jan 31, 2026
CVE Published
via MITRE·11:39 AM
Data Sourced
via MITRE·11:39 AM
Description
Data Sourced
via NVD·12:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-23024?

CVE-2026-23024 is classified as a medium severity vulnerability due to its potential impact on system performance.

2

How do I fix CVE-2026-23024?

To fix CVE-2026-23024, ensure that your Linux kernel is updated to the latest version where this vulnerability has been patched.

3

What systems are affected by CVE-2026-23024?

CVE-2026-23024 affects the Linux kernel, specifically in scenarios involving flow steering list maintenance during module removal.

4

What are the potential consequences of CVE-2026-23024?

The potential consequences of CVE-2026-23024 include memory leaks that could lead to degraded system performance over time.

5

Is there a workaround for CVE-2026-23024?

While the best practice is to apply the kernel update, temporarily avoiding the use of netlink-based tools may help mitigate the symptoms of this vulnerability.

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