🛡️ CVE-2024-26735 — 8300-firmware

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

• Attack vector: Local — a local account, shell or session on the host is needed.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: None.
• Integrity impact: None.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2024-26735 is classified as CWE-416: Use After Free. Memory is used after being released, so its contents may already belong to something else.

Affected software

CVE-2024-26735 is recorded against 11 packages.

• 8300-firmware
• 8700-firmware
• a400-firmware
• c400-firmware
• debian-linux
• e-series-santricity-os-controller (from 11.0.0 up to 11.70.2)
• h610c-firmware
• h610s-firmware
• h615c-firmware
• kernel (from 6.7.0 up to 6.7.7)
• linux-kernel

Timeline and source

Published on 3 April 2024 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
lists.debian.org
lists.debian.org
security.netapp.com

Other advisories for this package

8300-firmware has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2024-6387 (8.1 High, published 1 Jul 2024)
• CVE-2024-26733 (5.5 Medium, published 3 Apr 2024)
• CVE-2023-1077 (7.0 High, published 27 Mar 2023)
• CVE-2022-30594 (7.8 High, published 12 May 2022)

Same weakness in other software

These advisories are the same class of weakness (CWE-416: Use After Free) in other software:

• CVE-2022-21540 (5.3 Medium, published 8 May 2026)
• CVE-2022-50552 (7.8 High, published 7 Oct 2025)
• CVE-2022-50542 (7.8 High, published 7 Oct 2025)
• CVE-2022-50507 (7.8 High, published 4 Oct 2025)
• CVE-2022-50496 (7.8 High, published 4 Oct 2025)
• CVE-2022-50492 (7.8 High, published 4 Oct 2025)
• CVE-2022-50488 (7.8 High, published 4 Oct 2025)
• CVE-2022-50423 (7.8 High, published 1 Oct 2025)

CVE-2024-26735 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Affected Packages

References