BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-26957High confidence

s390/zcrypt: fix reference counting on zcrypt card objects

Linux · Linux

Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

15 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 11 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2024-26957 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: s390/zcrypt: fix reference counting on zcrypt card objects
198 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the s390/zcrypt component of the Linux kernel. An incorrect handling of reference counting on zcrypt card objects can lead to a use-after-free vulnerability. A local attacker could exploit this to cause a denial of service (DoS) or potentially achieve privilege escalation.
Remediation
No remediation text is recorded.
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: fix reference counting on zcrypt card objects.
Remediation
Update to V3.1.5 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-24219

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: fix reference counting on zcrypt card objects Tests with hot-plugging crytpo cards on KVM guests with debug kernel build revealed an use after free for the load field of the struct zcrypt_card. The reason was an incorrect reference handling of the zcrypt card object which could lead to a free of the zcrypt card object while it was still in use. This is an example of the slab message: kernel: 0x00000000885a7512-0x00000000885a7513 @offset=1298. First byte 0x68 instead of 0x6b kernel: Allocated in zcrypt_card_alloc+0x36/0x70 [zcrypt] age=18046 cpu=3 pid=43 kernel: kmalloc_trace+0x3f2/0x470 kernel: zcrypt_card_alloc+0x36/0x70 [zcrypt] kernel: zcrypt_cex4_card_probe+0x26/0x380 [zcrypt_cex4] kernel: ap_device_probe+0x15c/0x290 kernel: really_probe+0xd2/0x468 kernel: driver_probe_device+0x40/0xf0 kernel: __device_attach_driver+0xc0/0x140 kernel: bus_for_each_drv+0x8c/0xd0 kernel: __device_attach+0x114/0x198 kernel: bus_probe_device+0xb4/0xc8 kernel: device_add+0x4d2/0x6e0 kernel: ap_scan_adapter+0x3d0/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: Freed in zcrypt_card_put+0x54/0x80 [zcrypt] age=9024 cpu=3 pid=43 kernel: kfree+0x37e/0x418 kernel: zcrypt_card_put+0x54/0x80 [zcrypt] kernel: ap_device_remove+0x4c/0xe0 kernel: device_release_driver_internal+0x1c4/0x270 kernel: bus_remove_device+0x100/0x188 kernel: device_del+0x164/0x3c0 kernel: device_unregister+0x30/0x90 kernel: ap_scan_adapter+0xc8/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: kthread+0x150/0x168 kernel: __ret_from_fork+0x3c/0x58 kernel: ret_from_fork+0xa/0x30 kernel: Slab 0x00000372022169c0 objects=20 used=18 fp=0x00000000885a7c88 flags=0x3ffff00000000a00(workingset|slab|node=0|zone=1|lastcpupid=0x1ffff) kernel: Object 0x00000000885a74b8 @offset=1208 fp=0x00000000885a7c88 kernel: Redzone 00000000885a74b0: bb bb bb bb bb bb bb bb ........ kernel: Object 00000000885a74b8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74c8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74d8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74e8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74f8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a7508: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 68 4b 6b 6b 6b a5 kkkkkkkkkkhKkkk. kernel: Redzone 00000000885a7518: bb bb bb bb bb bb bb bb ........ kernel: Padding 00000000885a756c: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZZZZZ kernel: CPU: 0 PID: 387 Comm: systemd-udevd Not tainted 6.8.0-HF #2 kernel: Hardware name: IBM 3931 A01 704 (KVM/Linux) kernel: Call Trace: kernel: [<00000000ca5ab5b8>] dump_stack_lvl+0x90/0x120 kernel: [<00000000c99d78bc>] check_bytes_and_report+0x114/0x140 kernel: [<00000000c99d53cc>] check_object+0x334/0x3f8 kernel: [<00000000c99d820c>] alloc_debug_processing+0xc4/0x1f8 kernel: [<00000000c99d852e>] get_partial_node.part.0+0x1ee/0x3e0 kernel: [<00000000c99d94ec>] ___slab_alloc+0xaf4/0x13c8 kernel: [<00000000c99d9e38>] __slab_alloc.constprop.0+0x78/0xb8 kernel: [<00000000c99dc8dc>] __kmalloc+0x434/0x590 kernel: [<00000000c9b4c0ce>] ext4_htree_store_dirent+0x4e/0x1c0 kernel: [<00000000c9b908a2>] htree_dirblock_to_tree+0x17a/0x3f0 kernel: ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: fix reference counting on zcrypt card objects Tests with hot-plugging crytpo cards on KVM guests with debug kernel build revealed an use after free for the load field of the struct zcrypt_card. The reason was an incorrect reference handling of the zcrypt card object which could lead to a free of the zcrypt card object while it was still in use. This is an example of the slab message: kernel: 0x00000000885a7512-0x00000000885a7513 @offset=1298. First byte 0x68 instead of 0x6b kernel: Allocated in zcrypt_card_alloc+0x36/0x70 [zcrypt] age=18046 cpu=3 pid=43 kernel: kmalloc_trace+0x3f2/0x470 kernel: zcrypt_card_alloc+0x36/0x70 [zcrypt] kernel: zcrypt_cex4_card_probe+0x26/0x380 [zcrypt_cex4] kernel: ap_device_probe+0x15c/0x290 kernel: really_probe+0xd2/0x468 kernel: driver_probe_device+0x40/0xf0 kernel: __device_attach_driver+0xc0/0x140 kernel: bus_for_each_drv+0x8c/0xd0 kernel: __device_attach+0x114/0x198 kernel: bus_probe_device+0xb4/0xc8 kernel: device_add+0x4d2/0x6e0 kernel: ap_scan_adapter+0x3d0/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: Freed in zcrypt_card_put+0x54/0x80 [zcrypt] age=9024 cpu=3 pid=43 kernel: kfree+0x37e/0x418 kernel: zcrypt_card_put+0x54/0x80 [zcrypt] kernel: ap_device_remove+0x4c/0xe0 kernel: device_release_driver_internal+0x1c4/0x270 kernel: bus_remove_device+0x100/0x188 kernel: device_del+0x164/0x3c0 kernel: device_unregister+0x30/0x90 kernel: ap_scan_adapter+0xc8/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: kthread+0x150/0x168 kernel: __ret_from_fork+0x3c/0x58 kernel: ret_from_fork+0xa/0x30 kernel: Slab 0x00000372022169c0 objects=20 used=18 fp=0x00000000885a7c88 flags=0x3ffff00000000a00(workingset|slab|node=0|zone=1|lastcpupid=0x1ffff) kernel: Object 0x00000000885a74b8 @offset=1208 fp=0x00000000885a7c88 kernel: Redzone 00000000885a74b0: bb bb bb bb bb bb bb bb ........ kernel: Object 00000000885a74b8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74c8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74d8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74e8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74f8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a7508: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 68 4b 6b 6b 6b a5 kkkkkkkkkkhKkkk. kernel: Redzone 00000000885a7518: bb bb bb bb bb bb bb bb ........ kernel: Padding 00000000885a756c: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZZZZZ kernel: CPU: 0 PID: 387 Comm: systemd-udevd Not tainted 6.8.0-HF #2 kernel: Hardware name: IBM 3931 A01 704 (KVM/Linux) kernel: Call Trace: kernel: [<00000000ca5ab5b8>] dump_stack_lvl+0x90/0x120 kernel: [<00000000c99d78bc>] check_bytes_and_report+0x114/0x140 kernel: [<00000000c99d53cc>] check_object+0x334/0x3f8 kernel: [<00000000c99d820c>] alloc_debug_processing+0xc4/0x1f8 kernel: [<00000000c99d852e>] get_partial_node.part.0+0x1ee/0x3e0 kernel: [<00000000c99d94ec>] ___slab_alloc+0xaf4/0x13c8 kernel: [<00000000c99d9e38>] __slab_alloc.constprop.0+0x78/0xb8 kernel: [<00000000c99dc8dc>] __kmalloc+0x434/0x590 kernel: [<00000000c9b4c0ce>] ext4_htree_store_dirent+0x4e/0x1c0 kernel: [<00000000c9b908a2>] htree_dirblock_to_tree+0x17a/0x3f0 kernel: ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: fix reference counting on zcrypt card objects Tests with hot-plugging crytpo cards on KVM guests with debug kernel build revealed an use after free for the load field of the struct zcrypt_card. The reason was an incorrect reference handling of the zcrypt card object which could lead to a free of the zcrypt card object while it was still in use. This is an example of the slab message: kernel: 0x00000000885a7512-0x00000000885a7513 @offset=1298. First byte 0x68 instead of 0x6b kernel: Allocated in zcrypt_card_alloc+0x36/0x70 [zcrypt] age=18046 cpu=3 pid=43 kernel: kmalloc_trace+0x3f2/0x470 kernel: zcrypt_card_alloc+0x36/0x70 [zcrypt] kernel: zcrypt_cex4_card_probe+0x26/0x380 [zcrypt_cex4] kernel: ap_device_probe+0x15c/0x290 kernel: really_probe+0xd2/0x468 kernel: driver_probe_device+0x40/0xf0 kernel: __device_attach_driver+0xc0/0x140 kernel: bus_for_each_drv+0x8c/0xd0 kernel: __device_attach+0x114/0x198 kernel: bus_probe_device+0xb4/0xc8 kernel: device_add+0x4d2/0x6e0 kernel: ap_scan_adapter+0x3d0/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: Freed in zcrypt_card_put+0x54/0x80 [zcrypt] age=9024 cpu=3 pid=43 kernel: kfree+0x37e/0x418 kernel: zcrypt_card_put+0x54/0x80 [zcrypt] kernel: ap_device_remove+0x4c/0xe0 kernel: device_release_driver_internal+0x1c4/0x270 kernel: bus_remove_device+0x100/0x188 kernel: device_del+0x164/0x3c0 kernel: device_unregister+0x30/0x90 kernel: ap_scan_adapter+0xc8/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: kthread+0x150/0x168 kernel: __ret_from_fork+0x3c/0x58 kernel: ret_from_fork+0xa/0x30 kernel: Slab 0x00000372022169c0 objects=20 used=18 fp=0x00000000885a7c88 flags=0x3ffff00000000a00(workingset|slab|node=0|zone=1|lastcpupid=0x1ffff) kernel: Object 0x00000000885a74b8 @offset=1208 fp=0x00000000885a7c88 kernel: Redzone 00000000885a74b0: bb bb bb bb bb bb bb bb ........ kernel: Object 00000000885a74b8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74c8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74d8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74e8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74f8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a7508: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 68 4b 6b 6b 6b a5 kkkkkkkkkkhKkkk. kernel: Redzone 00000000885a7518: bb bb bb bb bb bb bb bb ........ kernel: Padding 00000000885a756c: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZZZZZ kernel: CPU: 0 PID: 387 Comm: systemd-udevd Not tainted 6.8.0-HF #2 kernel: Hardware name: IBM 3931 A01 704 (KVM/Linux) kernel: Call Trace: kernel: [<00000000ca5ab5b8>] dump_stack_lvl+0x90/0x120 kernel: [<00000000c99d78bc>] check_bytes_and_report+0x114/0x140 kernel: [<00000000c99d53cc>] check_object+0x334/0x3f8 kernel: [<00000000c99d820c>] alloc_debug_processing+0xc4/0x1f8 kernel: [<00000000c99d852e>] get_partial_node.part.0+0x1ee/0x3e0 kernel: [<00000000c99d94ec>] ___slab_alloc+0xaf4/0x13c8 kernel: [<00000000c99d9e38>] __slab_alloc.constprop.0+0x78/0xb8 kernel: [<00000000c99dc8dc>] __kmalloc+0x434/0x590 kernel: [<00000000c9b4c0ce>] ext4_htree_store_dirent+0x4e/0x1c0 kernel: [<00000000c9b908a2>] htree_dirblock_to_tree+0x17a/0x3f0 kernel: ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0225Dell PowerProtect Data Domain: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um erhöhte Rechte zu erlangen, einen Denial-of-Service-Zustand herbeizuführen und einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1008Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder sonstige Auswirkungen zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240508Security Bulletin 08 May 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 08 May 2024, published on 8 May 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0799Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26936 https://www.cve.org/CVERecord?id=CVE-2024-26936 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26952 https://www.cve.org/CVERecord?id=CVE-2024-26952 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=CVE-2024-26965 Référence CVE CVE-2024-26966 https://www.cve.org/CVERecord?id=CVE-2024-26966 Référence CVE CVE-2024-26969 https://www.cve.org/CVERecord?id=CVE-2024-26969 Référence CVE CVE-2024-26970 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0717Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-26940 Référence CVE CVE-2024-26943 https://www.cve.org/CVERecord?id=CVE-2024-26943 Référence CVE CVE-2024-26944 https://www.cve.org/CVERecord?id=CVE-2024-26944 Référence CVE CVE-2024-26945 https://www.cve.org/CVERecord?id=CVE-2024-26945 Référence CVE CVE-2024-26946 https://www.cve.org/CVERecord?id=CVE-2024-26946 Référence CVE CVE-2024-26948 https://www.cve.org/CVERecord?id=CVE-2024-26948 Référence CVE CVE-2024-26949 https://www.cve.org/CVERecord?id=CVE-2024-26949 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26962 https://www.cve.org/CVERecord?id=CVE-2024-26962 Référence CVE CVE-2024-26963 https://www.cve.org/CVERecord?id=CVE-2024-26963 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26972 https://www.cve.org/CVERecord?id=CVE-2024-26972 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0645Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26936 https://www.cve.org/CVERecord?id=CVE-2024-26936 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26952 https://www.cve.org/CVERecord?id=CVE-2024-26952 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=CVE-2024-26965 Référence CVE CVE-2024-26966 https://www.cve.org/CVERecord?id=CVE-2024-26966 Référence CVE CVE-2024-26969 https://www.cve.org/CVERecord?id=CVE-2024-26969 Référence CVE CVE-2024-26970 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0633Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-26931 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26936 https://www.cve.org/CVERecord?id=CVE-2024-26936 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=CVE-2024-26965 Référence CVE CVE-2024-26966 https://www.cve.org/CVERecord?id=CVE-2024-26966 Référence CVE CVE-2024-26969 https://www.cve.org/CVERecord?id=CVE-2024-26969 Référence CVE CVE-2024-26970 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0611Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-26931 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26936 https://www.cve.org/CVERecord?id=CVE-2024-26936 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=CVE-2024-26965 Référence CVE CVE-2024-26966 https://www.cve.org/CVERecord?id=CVE-2024-26966 Référence CVE CVE-2024-26969 https://www.cve.org/CVERecord?id=CVE-2024-26969 Référence CVE CVE-2024-26970 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0546Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-26948 Référence CVE CVE-2024-26949 https://www.cve.org/CVERecord?id=CVE-2024-26949 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26952 https://www.cve.org/CVERecord?id=CVE-2024-26952 Référence CVE CVE-2024-26953 https://www.cve.org/CVERecord?id=CVE-2024-26953 Référence CVE CVE-2024-26954 https://www.cve.org/CVERecord?id=CVE-2024-26954 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26959 https://www.cve.org/CVERecord?id=CVE-2024-26959 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26962 https://www.cve.org/CVERecord?id=CVE-2024-26962 Référence CVE CVE-2024-26963 https://www.cve.org/CVERecord?id=CVE-2024-26963 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0527Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-26926 Référence CVE CVE-2024-26931 https://www.cve.org/CVERecord?id=CVE-2024-26931 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=CVE-2024-26965 Référence CVE CVE-2024-26966 https://www.cve.org/CVERecord?id=CVE-2024-26966 Référence CVE CVE-2024-26969 https://www.cve.org/CVERecord?id=CVE-2024-26969 Référence CVE CVE-2024-26970 https://www.cve.org/CVERecord?id=CVE-2024-26970 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0526Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-26940 Référence CVE CVE-2024-26943 https://www.cve.org/CVERecord?id=CVE-2024-26943 Référence CVE CVE-2024-26945 https://www.cve.org/CVERecord?id=CVE-2024-26945 Référence CVE CVE-2024-26946 https://www.cve.org/CVERecord?id=CVE-2024-26946 Référence CVE CVE-2024-26948 https://www.cve.org/CVERecord?id=CVE-2024-26948 Référence CVE CVE-2024-26949 https://www.cve.org/CVERecord?id=CVE-2024-26949 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26962 https://www.cve.org/CVERecord?id=CVE-2024-26962 Référence CVE CVE-2024-26963 https://www.cve.org/CVERecord?id=CVE-2024-26963 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26972 https://www.cve.org/CVERecord?id=CVE-2024-26972 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0496Multiples vulnérabilités dans le noyau Linux de SUSE

id=CVE-2024-26931 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-269355 https://www.cve.org/CVERecord?id=CVE-2024-269355 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26938 https://www.cve.org/CVERecord?id=CVE-2024-26938 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-26940 https://www.cve.org/CVERecord?id=CVE-2024-26940 Référence CVE CVE-2024-26943 https://www.cve.org/CVERecord?id=CVE-2024-26943 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26977 https://www.cve.org/CVERecord?id=CVE-2024-26977 Référence CVE CVE-2024-26979 https://www.cve.org/CVERecord?id=CVE-2024-26979 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-26988 https://www.cve.org/CVERecord?id=CVE-2024-26988 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0381Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26936 https://www.cve.org/CVERecord?id=CVE-2024-26936 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?id=CVE-2024-26957 Référence CVE CVE-2024-26958 https://www.cve.org/CVERecord?id=CVE-2024-26958 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=CVE-2024-26965 Référence CVE CVE-2024-26966 https://www.cve.org/CVERecord?id=CVE-2024-26966 Référence CVE CVE-2024-26969 https://www.cve.org/CVERecord?id=CVE-2024-26969 Référence CVE CVE-2024-26970 https://www.cve.org/CVERecord?id=CVE-2024-26970 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-020871Linux の Linux Kernel 等複数ベンダの製品における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel 等複数ベンダの製品には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.10, 4.19.312 ≤ 4.19.*, 5.4.274 ≤ 5.4.*, 5.10.215 ≤ 5.10.*, 5.15.154 ≤ 5.15.*, 6.1.84 ≤ 6.1.*, 6.6.24 ≤ 6.6.*, 6.7.12 ≤ 6.7.*, 6.8.3 ≤ 6.8.*, 6.9 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 May 2024 · Last source change 5 Aug 2026, 11:28 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-24219
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-24219↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-398330↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-26957 · cve.blacktree.nl