BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-56587High confidence

leds: class: Protect brightness_show() with led_cdev->led_access mutex

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

19 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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 record ↗Source updated 8 Sept 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.

1 current
SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2
3 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
leds: class: Protect brightness_show() with led_cdev->led_access mutex. There is NULL pointer vulnerability observed if from Process A where hid device being added which results in adding a led_cdev addition and later a another call to access of led_cdev attribute from Process B can result in NULL pointer vulnerability.
Remediation
Update to V3.2 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.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-53235

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: leds: class: Protect brightness_show() with led_cdev->led_access mutex There is NULL pointer issue observed if from Process A where hid device being added which results in adding a led_cdev addition and later a another call to access of led_cdev attribute from Process B can result in NULL pointer issue. Use mutex led_cdev->led_access to protect access to led->cdev and its attribute inside brightness_show() and max_brightness_show() and also update the comment for mutex that it should be used to protect the led class device fields. Process A Process B kthread+0x114 worker_thread+0x244 process_scheduled_works+0x248 uhid_device_add_worker+0x24 hid_add_device+0x120 device_add+0x268 bus_probe_device+0x94 device_initial_probe+0x14 __device_attach+0xfc bus_for_each_drv+0x10c __device_attach_driver+0x14c driver_probe_device+0x3c __driver_probe_device+0xa0 really_probe+0x190 hid_device_probe+0x130 ps_probe+0x990 ps_led_register+0x94 devm_led_classdev_register_ext+0x58 led_classdev_register_ext+0x1f8 device_create_with_groups+0x48 device_create_groups_vargs+0xc8 device_add+0x244 kobject_uevent+0x14 kobject_uevent_env[jt]+0x224 mutex_unlock[jt]+0xc4 __mutex_unlock_slowpath+0xd4 wake_up_q+0x70 try_to_wake_up[jt]+0x48c preempt_schedule_common+0x28 __schedule+0x628 __switch_to+0x174 el0t_64_sync+0x1a8/0x1ac el0t_64_sync_handler+0x68/0xbc el0_svc+0x38/0x68 do_el0_svc+0x1c/0x28 el0_svc_common+0x80/0xe0 invoke_syscall+0x58/0x114 __arm64_sys_read+0x1c/0x2c ksys_read+0x78/0xe8 vfs_read+0x1e0/0x2c8 kernfs_fop_read_iter+0x68/0x1b4 seq_read_iter+0x158/0x4ec kernfs_seq_show+0x44/0x54 sysfs_kf_seq_show+0xb4/0x130 dev_attr_show+0x38/0x74 brightness_show+0x20/0x4c dualshock4_led_get_brightness+0xc/0x74 [ 3313.874295][ T4013] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000060 [ 3313.874301][ T4013] Mem abort info: [ 3313.874303][ T4013] ESR = 0x0000000096000006 [ 3313.874305][ T4013] EC = 0x25: DABT (current EL), IL = 32 bits [ 3313.874307][ T4013] SET = 0, FnV = 0 [ 3313.874309][ T4013] EA = 0, S1PTW = 0 [ 3313.874311][ T4013] FSC = 0x06: level 2 translation fault [ 3313.874313][ T4013] Data abort info: [ 3313.874314][ T4013] ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000 [ 3313.874316][ T4013] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 3313.874318][ T4013] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 3313.874320][ T4013] user pgtable: 4k pages, 39-bit VAs, pgdp=00000008f2b0a000 .. [ 3313.874332][ T4013] Dumping ftrace buffer: [ 3313.874334][ T4013] (ftrace buffer empty) .. .. [ dd3313.874639][ T4013] CPU: 6 PID: 4013 Comm: InputReader [ 3313.874648][ T4013] pc : dualshock4_led_get_brightness+0xc/0x74 [ 3313.874653][ T4013] lr : led_update_brightness+0x38/0x60 [ 3313.874656][ T4013] sp : ffffffc0b910bbd0 .. .. [ 3313.874685][ T4013] Call trace: [ 3313.874687][ T4013] dualshock4_led_get_brightness+0xc/0x74 [ 3313.874690][ T4013] brightness_show+0x20/0x4c [ 3313.874692][ T4013] dev_attr_show+0x38/0x74 [ 3313.874696][ T4013] sysfs_kf_seq_show+0xb4/0x130 [ 3313.874700][ T4013] kernfs_seq_show+0x44/0x54 [ 3313.874703][ T4013] seq_read_iter+0x158/0x4ec [ 3313.874705][ T4013] kernfs_fop_read_iter+0x68/0x1b4 [ 3313.874708][ T4013] vfs_read+0x1e0/0x2c8 [ 3313.874711][ T4013] ksys_read+0x78/0xe8 [ 3313.874714][ T4013] __arm64_sys_read+0x1c/0x2c [ 3313.874718][ T4013] invoke_syscall+0x58/0x114 [ 3313.874721][ T4013] el0_svc_common+0x80/0xe0 [ 3313.874724][ T4013] do_el0_svc+0x1c/0x28 [ 3313.874727][ T4013] el0_svc+0x38/0x68 [ 3313.874730][ T4013] el0t_64_sync_handler+0x68/0xbc [ 3313.874732][ T4013] el0t_64_sync+0x1a8/0x1ac

What

In the Linux kernel, the following vulnerability has been resolved: leds: class: Protect brightness_show() with led_cdev->led_access mutex There is NULL pointer issue observed if from Process A where hid device being added which results in adding a led_cdev addition and later a another call to access of led_cdev attribute from Process B can result in NULL pointer issue. Use mutex led_cdev->led_access to protect access to led->cdev and its attribute inside brightness_show() and max_brightness_show() and also update the comment for mutex that it should be used to protect the led class device fields. Process A Process B kthread+0x114 worker_thread+0x244 process_scheduled_works+0x248 uhid_device_add_worker+0x24 hid_add_device+0x120 device_add+0x268 bus_probe_device+0x94 device_initial_probe+0x14 __device_attach+0xfc bus_for_each_drv+0x10c __device_attach_driver+0x14c driver_probe_device+0x3c __driver_probe_device+0xa0 really_probe+0x190 hid_device_probe+0x130 ps_probe+0x990 ps_led_register+0x94 devm_led_classdev_register_ext+0x58 led_classdev_register_ext+0x1f8 device_create_with_groups+0x48 device_create_groups_vargs+0xc8 device_add+0x244 kobject_uevent+0x14 kobject_uevent_env[jt]+0x224 mutex_unlock[jt]+0xc4 __mutex_unlock_slowpath+0xd4 wake_up_q+0x70 try_to_wake_up[jt]+0x48c preempt_schedule_common+0x28 __schedule+0x628 __switch_to+0x174 el0t_64_sync+0x1a8/0x1ac el0t_64_sync_handler+0x68/0xbc el0_svc+0x38/0x68 do_el0_svc+0x1c/0x28 el0_svc_common+0x80/0xe0 invoke_syscall+0x58/0x114 __arm64_sys_read+0x1c/0x2c ksys_read+0x78/0xe8 vfs_read+0x1e0/0x2c8 kernfs_fop_read_iter+0x68/0x1b4 seq_read_iter+0x158/0x4ec kernfs_seq_show+0x44/0x54 sysfs_kf_seq_show+0xb4/0x130 dev_attr_show+0x38/0x74 brightness_show+0x20/0x4c dualshock4_led_get_brightness+0xc/0x74 [ 3313.874295][ T4013] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000060 [ 3313.874301][ T4013] Mem abort info: [ 3313.874303][ T4013] ESR = 0x0000000096000006 [ 3313.874305][ T4013] EC = 0x25: DABT (current EL), IL = 32 bits [ 3313.874307][ T4013] SET = 0, FnV = 0 [ 3313.874309][ T4013] EA = 0, S1PTW = 0 [ 3313.874311][ T4013] FSC = 0x06: level 2 translation fault [ 3313.874313][ T4013] Data abort info: [ 3313.874314][ T4013] ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000 [ 3313.874316][ T4013] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 3313.874318][ T4013] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 3313.874320][ T4013] user pgtable: 4k pages, 39-bit VAs, pgdp=00000008f2b0a000 .. [ 3313.874332][ T4013] Dumping ftrace buffer: [ 3313.874334][ T4013] (ftrace buffer empty) .. .. [ dd3313.874639][ T4013] CPU: 6 PID: 4013 Comm: InputReader [ 3313.874648][ T4013] pc : dualshock4_led_get_brightness+0xc/0x74 [ 3313.874653][ T4013] lr : led_update_brightness+0x38/0x60 [ 3313.874656][ T4013] sp : ffffffc0b910bbd0 .. .. [ 3313.874685][ T4013] Call trace: [ 3313.874687][ T4013] dualshock4_led_get_brightness+0xc/0x74 [ 3313.874690][ T4013] brightness_show+0x20/0x4c [ 3313.874692][ T4013] dev_attr_show+0x38/0x74 [ 3313.874696][ T4013] sysfs_kf_seq_show+0xb4/0x130 [ 3313.874700][ T4013] kernfs_seq_show+0x44/0x54 [ 3313.874703][ T4013] seq_read_iter+0x158/0x4ec [ 3313.874705][ T4013] kernfs_fop_read_iter+0x68/0x1b4 [ 3313.874708][ T4013] vfs_read+0x1e0/0x2c8 [ 3313.874711][ T4013] ksys_read+0x78/0xe8 [ 3313.874714][ T4013] __arm64_sys_read+0x1c/0x2c [ 3313.874718][ T4013] invoke_syscall+0x58/0x114 [ 3313.874721][ T4013] el0_svc_common+0x80/0xe0 [ 3313.874724][ T4013] do_el0_svc+0x1c/0x28 [ 3313.874727][ T4013] el0_svc+0x38/0x68 [ 3313.874730][ T4013] el0t_64_sync_handler+0x68/0xbc [ 3313.874732][ T4013] el0t_64_sync+0x1a8/0x1ac

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: leds: class: Protect brightness_show() with led_cdev->led_access mutex There is NULL pointer issue observed if from Process A where hid device being added which results in adding a led_cdev addition and later a another call to access of led_cdev attribute from Process B can result in NULL pointer issue. Use mutex led_cdev->led_access to protect access to led->cdev and its attribute inside brightness_show() and max_brightness_show() and also update the comment for mutex that it should be used to protect the led class device fields. Process A Process B kthread+0x114 worker_thread+0x244 process_scheduled_works+0x248 uhid_device_add_worker+0x24 hid_add_device+0x120 device_add+0x268 bus_probe_device+0x94 device_initial_probe+0x14 __device_attach+0xfc bus_for_each_drv+0x10c __device_attach_driver+0x14c driver_probe_device+0x3c __driver_probe_device+0xa0 really_probe+0x190 hid_device_probe+0x130 ps_probe+0x990 ps_led_register+0x94 devm_led_classdev_register_ext+0x58 led_classdev_register_ext+0x1f8 device_create_with_groups+0x48 device_create_groups_vargs+0xc8 device_add+0x244 kobject_uevent+0x14 kobject_uevent_env[jt]+0x224 mutex_unlock[jt]+0xc4 __mutex_unlock_slowpath+0xd4 wake_up_q+0x70 try_to_wake_up[jt]+0x48c preempt_schedule_common+0x28 __schedule+0x628 __switch_to+0x174 el0t_64_sync+0x1a8/0x1ac el0t_64_sync_handler+0x68/0xbc el0_svc+0x38/0x68 do_el0_svc+0x1c/0x28 el0_svc_common+0x80/0xe0 invoke_syscall+0x58/0x114 __arm64_sys_read+0x1c/0x2c ksys_read+0x78/0xe8 vfs_read+0x1e0/0x2c8 kernfs_fop_read_iter+0x68/0x1b4 seq_read_iter+0x158/0x4ec kernfs_seq_show+0x44/0x54 sysfs_kf_seq_show+0xb4/0x130 dev_attr_show+0x38/0x74 brightness_show+0x20/0x4c dualshock4_led_get_brightness+0xc/0x74 [ 3313.874295][ T4013] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000060 [ 3313.874301][ T4013] Mem abort info: [ 3313.874303][ T4013] ESR = 0x0000000096000006 [ 3313.874305][ T4013] EC = 0x25: DABT (current EL), IL = 32 bits [ 3313.874307][ T4013] SET = 0, FnV = 0 [ 3313.874309][ T4013] EA = 0, S1PTW = 0 [ 3313.874311][ T4013] FSC = 0x06: level 2 translation fault [ 3313.874313][ T4013] Data abort info: [ 3313.874314][ T4013] ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000 [ 3313.874316][ T4013] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 3313.874318][ T4013] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 3313.874320][ T4013] user pgtable: 4k pages, 39-bit VAs, pgdp=00000008f2b0a000 .. [ 3313.874332][ T4013] Dumping ftrace buffer: [ 3313.874334][ T4013] (ftrace buffer empty) .. .. [ dd3313.874639][ T4013] CPU: 6 PID: 4013 Comm: InputReader [ 3313.874648][ T4013] pc : dualshock4_led_get_brightness+0xc/0x74 [ 3313.874653][ T4013] lr : led_update_brightness+0x38/0x60 [ 3313.874656][ T4013] sp : ffffffc0b910bbd0 .. .. [ 3313.874685][ T4013] Call trace: [ 3313.874687][ T4013] dualshock4_led_get_brightness+0xc/0x74 [ 3313.874690][ T4013] brightness_show+0x20/0x4c [ 3313.874692][ T4013] dev_attr_show+0x38/0x74 [ 3313.874696][ T4013] sysfs_kf_seq_show+0xb4/0x130 [ 3313.874700][ T4013] kernfs_seq_show+0x44/0x54 [ 3313.874703][ T4013] seq_read_iter+0x158/0x4ec [ 3313.874705][ T4013] kernfs_fop_read_iter+0x68/0x1b4 [ 3313.874708][ T4013] vfs_read+0x1e0/0x2c8 [ 3313.874711][ T4013] ksys_read+0x78/0xe8 [ 3313.874714][ T4013] __arm64_sys_read+0x1c/0x2c [ 3313.874718][ T4013] invoke_syscall+0x58/0x114 [ 3313.874721][ T4013] el0_svc_common+0x80/0xe0 [ 3313.874724][ T4013] do_el0_svc+0x1c/0x28 [ 3313.874727][ T4013] el0_svc+0x38/0x68 [ 3313.874730][ T4013] el0t_64_sync_handler+0x68/0xbc [ 3313.874732][ T4013] el0t_64_sync+0x1a8/0x1ac

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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-476

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-476
A

Official authority intelligence

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

BSI · German · WID-SEC-W-2024-3762Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2024-56568 Référence CVE CVE-2024-56569 https://www.cve.org/CVERecord?id=CVE-2024-56569 Référence CVE CVE-2024-56570 https://www.cve.org/CVERecord?id=CVE-2024-56570 Référence CVE CVE-2024-56571 https://www.cve.org/CVERecord?id=CVE-2024-56571 Référence CVE CVE-2024-56572 https://www.cve.org/CVERecord?id=CVE-2024-56572 Référence CVE CVE-2024-56574 https://www.cve.org/CVERecord?id=CVE-2024-56574 Référence CVE CVE-2024-56576 https://www.cve.org/CVERecord?id=CVE-2024-56576 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56586 https://www.cve.org/CVERecord?id=CVE-2024-56586 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56597 https://www.cve.org/CVERecord?id=CVE-2024-56597 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=CVE-2024-56598 Référence CVE CVE-2024-56600 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56577 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56579 https://www.cve.org/CVERecord?id=CVE-2024-56579 Référence CVE CVE-2024-56580 https://www.cve.org/CVERecord?id=CVE-2024-56580 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=CVE-2024-56583 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56586 https://www.cve.org/CVERecord?id=CVE-2024-56586 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56577 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56579 https://www.cve.org/CVERecord?id=CVE-2024-56579 Référence CVE CVE-2024-56580 https://www.cve.org/CVERecord?id=CVE-2024-56580 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=CVE-2024-56583 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56586 https://www.cve.org/CVERecord?id=CVE-2024-56586 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56569 Référence CVE CVE-2024-56570 https://www.cve.org/CVERecord?id=CVE-2024-56570 Référence CVE CVE-2024-56572 https://www.cve.org/CVERecord?id=CVE-2024-56572 Référence CVE CVE-2024-56574 https://www.cve.org/CVERecord?id=CVE-2024-56574 Référence CVE CVE-2024-56575 https://www.cve.org/CVERecord?id=CVE-2024-56575 Référence CVE CVE-2024-56576 https://www.cve.org/CVERecord?id=CVE-2024-56576 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56586 https://www.cve.org/CVERecord?id=CVE-2024-56586 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56597 https://www.cve.org/CVERecord?id=CVE-2024-56597 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56570 Référence CVE CVE-2024-56572 https://www.cve.org/CVERecord?id=CVE-2024-56572 Référence CVE CVE-2024-56574 https://www.cve.org/CVERecord?id=CVE-2024-56574 Référence CVE CVE-2024-56575 https://www.cve.org/CVERecord?id=CVE-2024-56575 Référence CVE CVE-2024-56576 https://www.cve.org/CVERecord?id=CVE-2024-56576 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56586 https://www.cve.org/CVERecord?id=CVE-2024-56586 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56597 https://www.cve.org/CVERecord?id=CVE-2024-56597 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56577 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56579 https://www.cve.org/CVERecord?id=CVE-2024-56579 Référence CVE CVE-2024-56580 https://www.cve.org/CVERecord?id=CVE-2024-56580 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=CVE-2024-56583 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56586 https://www.cve.org/CVERecord?id=CVE-2024-56586 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56591 https://www.cve.org/CVERecord?id=CVE-2024-56591 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56575 Référence CVE CVE-2024-56576 https://www.cve.org/CVERecord?id=CVE-2024-56576 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56579 https://www.cve.org/CVERecord?id=CVE-2024-56579 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56585 https://www.cve.org/CVERecord?id=CVE-2024-56585 Référence CVE CVE-2024-56586 https://www.cve.org/CVERecord?id=CVE-2024-56586 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56597 https://www.cve.org/CVERecord?id=CVE-2024-56597 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56570 Référence CVE CVE-2024-56571 https://www.cve.org/CVERecord?id=CVE-2024-56571 Référence CVE CVE-2024-56572 https://www.cve.org/CVERecord?id=CVE-2024-56572 Référence CVE CVE-2024-56573 https://www.cve.org/CVERecord?id=CVE-2024-56573 Référence CVE CVE-2024-56574 https://www.cve.org/CVERecord?id=CVE-2024-56574 Référence CVE CVE-2024-56575 https://www.cve.org/CVERecord?id=CVE-2024-56575 Référence CVE CVE-2024-56577 https://www.cve.org/CVERecord?id=CVE-2024-56577 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56570 Référence CVE CVE-2024-56571 https://www.cve.org/CVERecord?id=CVE-2024-56571 Référence CVE CVE-2024-56572 https://www.cve.org/CVERecord?id=CVE-2024-56572 Référence CVE CVE-2024-56573 https://www.cve.org/CVERecord?id=CVE-2024-56573 Référence CVE CVE-2024-56574 https://www.cve.org/CVERecord?id=CVE-2024-56574 Référence CVE CVE-2024-56575 https://www.cve.org/CVERecord?id=CVE-2024-56575 Référence CVE CVE-2024-56577 https://www.cve.org/CVERecord?id=CVE-2024-56577 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56572 Référence CVE CVE-2024-56573 https://www.cve.org/CVERecord?id=CVE-2024-56573 Référence CVE CVE-2024-56574 https://www.cve.org/CVERecord?id=CVE-2024-56574 Référence CVE CVE-2024-56575 https://www.cve.org/CVERecord?id=CVE-2024-56575 Référence CVE CVE-2024-56576 https://www.cve.org/CVERecord?id=CVE-2024-56576 Référence CVE CVE-2024-56577 https://www.cve.org/CVERecord?id=CVE-2024-56577 Référence CVE CVE-2024-56578 https://www.cve.org/CVERecord?id=CVE-2024-56578 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56587 https://www.cve.org/CVERecord?id=CVE-2024-56587 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56589 https://www.cve.org/CVERecord?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56597 https://www.cve.org/CVERecord?id=

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.
Patch available
Affected
RUGGEDCOM RST2428P (6GK6242-6PA00); SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family; SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Fixed
< 2.6.26; 5.4.287 ≤ 5.4.*; 5.10.231 ≤ 5.10.*; 5.15.174 ≤ 5.15.*; 6.1.120 ≤ 6.1.*; 6.6.66 ≤ 6.6.*; 6.12.5 ≤ 6.12.*; 6.13 ≤ *
Action
Update to V3.2 or later version
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 Dec 2024 · Last source change 11 May 2026, 20:55 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-53235
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
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-56587 · cve.blacktree.nl