Answer in brief
CVE-2024-43864 records a Unknown severity vulnerability in net/mlx5e: Fix CT entry update leaks of modify header context. 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 | >=94ceffb48eac7692677d8093dcde6965b70c4b35 <daab2cc17b6b6ab158566bba037e9551fd432b59 || >=94ceffb48eac7692677d8093dcde6965b70c4b35 <89064d09c56b44c668509bf793c410484f63f5ad || >=94ceffb48eac7692677d8093dcde6965b70c4b35 <025f2b85a5e5a46df14ecf162c3c80a957a36d0b | daab2cc17b6b6ab158566bba037e9551fd432b59, 89064d09c56b44c668509bf793c410484f63f5ad, 025f2b85a5e5a46df14ecf162c3c80a957a36d0b |
| Linux/Linuxgeneric | 6.3 | Not reported |
Published upstream
Aug 20, 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: net/mlx5e: Fix CT entry update leaks of modify header context The cited commit allocates a new modify header to replace the old one when updating CT entry. But if failed to allocate a new one, eg. exceed the max number firmware can support, modify header will be an error pointer that will trigger a panic when deallocating it. And the old modify header point is copied to old attr. When the old attr is freed, the old modify header is lost. Fix it by restoring the old attr to attr when failed to allocate a new modify header context. So when the CT entry is freed, the right modify header context will be freed. And the panic of accessing error pointer is also fixed.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-43864 records a Unknown severity vulnerability in net/mlx5e: Fix CT entry update leaks of modify header context. 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 | >=94ceffb48eac7692677d8093dcde6965b70c4b35 <daab2cc17b6b6ab158566bba037e9551fd432b59 || >=94ceffb48eac7692677d8093dcde6965b70c4b35 <89064d09c56b44c668509bf793c410484f63f5ad || >=94ceffb48eac7692677d8093dcde6965b70c4b35 <025f2b85a5e5a46df14ecf162c3c80a957a36d0b | daab2cc17b6b6ab158566bba037e9551fd432b59, 89064d09c56b44c668509bf793c410484f63f5ad, 025f2b85a5e5a46df14ecf162c3c80a957a36d0b |
| Linux/Linuxgeneric | 6.3 | Not reported |
Published upstream
Aug 20, 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: net/mlx5e: Fix CT entry update leaks of modify header context The cited commit allocates a new modify header to replace the old one when updating CT entry. But if failed to allocate a new one, eg. exceed the max number firmware can support, modify header will be an error pointer that will trigger a panic when deallocating it. And the old modify header point is copied to old attr. When the old attr is freed, the old modify header is lost. Fix it by restoring the old attr to attr when failed to allocate a new modify header context. So when the CT entry is freed, the right modify header context will be freed. And the panic of accessing error pointer is also fixed.
Quoted source text, attributed separately from HOL analysis.