CVE-2024-35879: of: dynamic: Synchronize of_changeset_destroy() with the devlink removals

Published May 19, 2024
·
Updated

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

of: dynamic: Synchronize ofchangesetdestroy() with the devlink removals

In the following sequence: 1) ofplatformdepopulate() 2) ofoverlayremove()

During the step 1, devices are destroyed and devlinks are removed. During the step 2, OF nodes are destroyed but ofchangesetentrydestroy() can raise warnings related to missing ofnodeput(): ERROR: memory leak, expected refcount 1 instead of 2 ...

Indeed, during the devlink removals performed at step 1, the removal itself releasing the device (and the attached ofnode) is done by a job queued in a workqueue and so, it is done asynchronously with respect to function calls. When the warning is present, ofnodeput() will be called but wrongly too late from the workqueue job.

In order to be sure that any ongoing devlink removals are done before the ofnode destruction, synchronize the ofchangesetdestroy() with the devlink removals.

Affected Software

15 affected componentsFixes available
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
Linux Linux kernel>=5.10.42<5.10.215
Linux Linux kernel>=5.12.9<5.13
Linux Linux kernel>=5.13.1<5.15.154
Linux Linux kernel>=5.16<6.1.85
Linux Linux kernel>=6.2<6.6.26
Linux Linux kernel>=6.7<6.8.5
Linux Linux kernel=5.13
Linux Linux kernel=5.13-rc4
Linux Linux kernel=5.13-rc5
Linux Linux kernel=5.13-rc6
Linux Linux kernel=5.13-rc7
Linux Linux kernel=6.9-rc1
Linux Linux kernel=6.9-rc2
Debian Debian Linux=10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Compensating control

    Synchronize of_changeset_destroy() with the devlink removals so that ongoing devlink removal jobs (queued in a workqueue at step 1) complete before the of_node destruction performed during the of_overlay_remove()/__of_changeset_entry_destroy() path.

Event History

May 19, 2024
CVE Published
via MITRE·08:34 AM
Data Sourced
via MITRE·08:34 AM
DescriptionSeverity
Data Sourced
via NVD·09:15 AM
Description
Data Sourced
via NVD·09:15 AM
RemedySeverityWeaknessAffected Software
Jul 11, 2024
Data Sourced
via Launchpad·07:46 PM
Description
May 1, 2025
Data Sourced
via Ubuntu·12:22 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-35879?

The severity of CVE-2024-35879 has been classified as moderate due to potential impacts on system stability.

2

How do I fix CVE-2024-35879?

To fix CVE-2024-35879, update to the latest version of the linux package, specifically to versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.9-1, or 6.12.10-1.

3

What systems are affected by CVE-2024-35879?

CVE-2024-35879 affects systems running specific versions of the Linux kernel, particularly those versions identified in the affected software list.

4

Is there a workaround for CVE-2024-35879?

A workaround for CVE-2024-35879 is not recommended; updating the kernel is the advised course of action.

5

When was CVE-2024-35879 disclosed?

CVE-2024-35879 was disclosed in 2024 as part of a series of Linux kernel vulnerabilities.

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