Answer in brief
CVE-2024-35879 records a Unknown severity vulnerability in of: dynamic: Synchronize of_changeset_destroy() with the devlink removals. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-35879 records a Unknown severity vulnerability in of: dynamic: Synchronize of_changeset_destroy() with the devlink removals. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.13 | Not reported |
| Linux/Linuxgeneric | >=d007150b4e15bfcb8d36cfd88a5645d42e44d383 <3127b2ee50c424a96eb3559fbb7b43cf0b111c7a || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <3ee2424107546d882e1ddd75333ca9c32879908c || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <7b6df050c45a1ea158fd50bc32a8e1447dd1e951 || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <801c8b8ec5bfb3519566dff16a5ecd48302fca82 || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <ae6d76e4f06c37a623e357e79d49b17411db6f5c || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <8917e7385346bd6584890ed362985c219fe6ae84 || 252c23915546863685ecc68cb3a39e7e80c6c9d4 || >=5.10.42 <5.10.215 || >=5.12.9 <5.13 | 3127b2ee50c424a96eb3559fbb7b43cf0b111c7a, 3ee2424107546d882e1ddd75333ca9c32879908c, 7b6df050c45a1ea158fd50bc32a8e1447dd1e951, 801c8b8ec5bfb3519566dff16a5ecd48302fca82, ae6d76e4f06c37a623e357e79d49b17411db6f5c, 8917e7385346bd6584890ed362985c219fe6ae84, 5.10.215, 5.13 |
Published upstream
May 19, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: of: dynamic: Synchronize of_changeset_destroy() with the devlink removals In the following sequence: 1) of_platform_depopulate() 2) of_overlay_remove() During the step 1, devices are destroyed and devlinks are removed. During the step 2, OF nodes are destroyed but __of_changeset_entry_destroy() can raise warnings related to missing of_node_put(): 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 of_node) 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, of_node_put() 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 of_node destruction, synchronize the of_changeset_destroy() with the devlink removals.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.13 | Not reported |
| Linux/Linuxgeneric | >=d007150b4e15bfcb8d36cfd88a5645d42e44d383 <3127b2ee50c424a96eb3559fbb7b43cf0b111c7a || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <3ee2424107546d882e1ddd75333ca9c32879908c || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <7b6df050c45a1ea158fd50bc32a8e1447dd1e951 || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <801c8b8ec5bfb3519566dff16a5ecd48302fca82 || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <ae6d76e4f06c37a623e357e79d49b17411db6f5c || >=80dd33cf72d1ab4f0af303f1fa242c6d6c8d328f <8917e7385346bd6584890ed362985c219fe6ae84 || 252c23915546863685ecc68cb3a39e7e80c6c9d4 || >=5.10.42 <5.10.215 || >=5.12.9 <5.13 | 3127b2ee50c424a96eb3559fbb7b43cf0b111c7a, 3ee2424107546d882e1ddd75333ca9c32879908c, 7b6df050c45a1ea158fd50bc32a8e1447dd1e951, 801c8b8ec5bfb3519566dff16a5ecd48302fca82, ae6d76e4f06c37a623e357e79d49b17411db6f5c, 8917e7385346bd6584890ed362985c219fe6ae84, 5.10.215, 5.13 |
Published upstream
May 19, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: of: dynamic: Synchronize of_changeset_destroy() with the devlink removals In the following sequence: 1) of_platform_depopulate() 2) of_overlay_remove() During the step 1, devices are destroyed and devlinks are removed. During the step 2, OF nodes are destroyed but __of_changeset_entry_destroy() can raise warnings related to missing of_node_put(): 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 of_node) 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, of_node_put() 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 of_node destruction, synchronize the of_changeset_destroy() with the devlink removals.
Quoted source text, attributed separately from HOL analysis.