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

rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu

Linux · Linux

4.7MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 19 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% 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: No default targetRemediation target: Normal maintenance

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

23 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 19 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.12.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-1Debian Security Tracker ↗Source updated 5 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-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 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-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 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-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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 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-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 Ubuntu Security ↗Source updated 5 Oct 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 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
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 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-53160 · CSAF 2.0 · revision 72 · interimSUSE Product Security TeamCVE-2024-53160
19 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP6
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu KCSAN reports a data race when access the krcp->monitor_work.timer.expires variable in the schedule_delayed_monitor_work() function: BUG: KCSAN: data-race in __mod_timer / kvfree_call_rcu read to 0xffff888237d1cce8 of 8 bytes by task 10149 on cpu 1: schedule_delayed_monitor_work kernel/rcu/tree.c:3520 [inline] kvfree_call_rcu+0x3b8/0x510 kernel/rcu/tree.c:3839 trie_update_elem+0x47c/0x620 kernel/bpf/lpm_trie.c:441 bpf_map_update_value+0x324/0x350 kernel/bpf/syscall.c:203 generic_map_update_batch+0x401/0x520 kernel/bpf/syscall.c:1849 bpf_map_do_batch+0x28c/0x3f0 kernel/bpf/syscall.c:5143 __sys_bpf+0x2e5/0x7a0 __do_sys_bpf kernel/bpf/syscall.c:5741 [inline] __se_sys_bpf kernel/bpf/syscall.c:5739 [inline] __x64_sys_bpf+0x43/0x50 kernel/bpf/syscall.c:5739 x64_sys_call+0x2625/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f write to 0xffff888237d1cce8 of 8 bytes by task 56 on cpu 0: __mod_timer+0x578/0x7f0 kernel/time/timer.c:1173 add_timer_global+0x51/0x70 kernel/time/timer.c:1330 __queue_delayed_work+0x127/0x1a0 kernel/workqueue.c:2523 queue_delayed_work_on+0xdf/0x190 kernel/workqueue.c:2552 queue_delayed_work include/linux/workqueue.h:677 [inline] schedule_delayed_monitor_work kernel/rcu/tree.c:3525 [inline] kfree_rcu_monitor+0x5e8/0x660 kernel/rcu/tree.c:3643 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391 kthread+0x1d1/0x210 kernel/kthread.c:389 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Reported by Kernel Concurrency Sanitizer on: CPU: 0 UID: 0 PID: 56 Comm: kworker/u8:4 Not tainted 6.12.0-rc2-syzkaller-00050-g5b7c893ed5ed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events_unbound kfree_rcu_monitor kfree_rcu_monitor() rearms the work if a "krcp" has to be still offloaded and this is done without holding krcp->lock, whereas the kvfree_call_rcu() holds it. Fix it by acquiring the "krcp->lock" for kfree_rcu_monitor() so both functions do not race anymore.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-53160 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Linux kernel. A race condition exists in the Read-Copy Update (RCU) subsystem during deferred memory freeing operations due to missing synchronization locks. A local user could exploit this vulnerability to cause a Denial of Service (DoS) through a kernel crash or system instability.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-51832

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 19 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: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu KCSAN reports a data race when access the krcp->monitor_work.timer.expires variable in the schedule_delayed_monitor_work() function: <snip> BUG: KCSAN: data-race in __mod_timer / kvfree_call_rcu read to 0xffff888237d1cce8 of 8 bytes by task 10149 on cpu 1: schedule_delayed_monitor_work kernel/rcu/tree.c:3520 [inline] kvfree_call_rcu+0x3b8/0x510 kernel/rcu/tree.c:3839 trie_update_elem+0x47c/0x620 kernel/bpf/lpm_trie.c:441 bpf_map_update_value+0x324/0x350 kernel/bpf/syscall.c:203 generic_map_update_batch+0x401/0x520 kernel/bpf/syscall.c:1849 bpf_map_do_batch+0x28c/0x3f0 kernel/bpf/syscall.c:5143 __sys_bpf+0x2e5/0x7a0 __do_sys_bpf kernel/bpf/syscall.c:5741 [inline] __se_sys_bpf kernel/bpf/syscall.c:5739 [inline] __x64_sys_bpf+0x43/0x50 kernel/bpf/syscall.c:5739 x64_sys_call+0x2625/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f write to 0xffff888237d1cce8 of 8 bytes by task 56 on cpu 0: __mod_timer+0x578/0x7f0 kernel/time/timer.c:1173 add_timer_global+0x51/0x70 kernel/time/timer.c:1330 __queue_delayed_work+0x127/0x1a0 kernel/workqueue.c:2523 queue_delayed_work_on+0xdf/0x190 kernel/workqueue.c:2552 queue_delayed_work include/linux/workqueue.h:677 [inline] schedule_delayed_monitor_work kernel/rcu/tree.c:3525 [inline] kfree_rcu_monitor+0x5e8/0x660 kernel/rcu/tree.c:3643 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391 kthread+0x1d1/0x210 kernel/kthread.c:389 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Reported by Kernel Concurrency Sanitizer on: CPU: 0 UID: 0 PID: 56 Comm: kworker/u8:4 Not tainted 6.12.0-rc2-syzkaller-00050-g5b7c893ed5ed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events_unbound kfree_rcu_monitor <snip> kfree_rcu_monitor() rearms the work if a "krcp" has to be still offloaded and this is done without holding krcp->lock, whereas the kvfree_call_rcu() holds it. Fix it by acquiring the "krcp->lock" for kfree_rcu_monitor() so both functions do not race anymore.

What

In the Linux kernel, the following vulnerability has been resolved: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu KCSAN reports a data race when access the krcp->monitor_work.timer.expires variable in the schedule_delayed_monitor_work() function: <snip> BUG: KCSAN: data-race in __mod_timer / kvfree_call_rcu read to 0xffff888237d1cce8 of 8 bytes by task 10149 on cpu 1: schedule_delayed_monitor_work kernel/rcu/tree.c:3520 [inline] kvfree_call_rcu+0x3b8/0x510 kernel/rcu/tree.c:3839 trie_update_elem+0x47c/0x620 kernel/bpf/lpm_trie.c:441 bpf_map_update_value+0x324/0x350 kernel/bpf/syscall.c:203 generic_map_update_batch+0x401/0x520 kernel/bpf/syscall.c:1849 bpf_map_do_batch+0x28c/0x3f0 kernel/bpf/syscall.c:5143 __sys_bpf+0x2e5/0x7a0 __do_sys_bpf kernel/bpf/syscall.c:5741 [inline] __se_sys_bpf kernel/bpf/syscall.c:5739 [inline] __x64_sys_bpf+0x43/0x50 kernel/bpf/syscall.c:5739 x64_sys_call+0x2625/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f write to 0xffff888237d1cce8 of 8 bytes by task 56 on cpu 0: __mod_timer+0x578/0x7f0 kernel/time/timer.c:1173 add_timer_global+0x51/0x70 kernel/time/timer.c:1330 __queue_delayed_work+0x127/0x1a0 kernel/workqueue.c:2523 queue_delayed_work_on+0xdf/0x190 kernel/workqueue.c:2552 queue_delayed_work include/linux/workqueue.h:677 [inline] schedule_delayed_monitor_work kernel/rcu/tree.c:3525 [inline] kfree_rcu_monitor+0x5e8/0x660 kernel/rcu/tree.c:3643 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391 kthread+0x1d1/0x210 kernel/kthread.c:389 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Reported by Kernel Concurrency Sanitizer on: CPU: 0 UID: 0 PID: 56 Comm: kworker/u8:4 Not tainted 6.12.0-rc2-syzkaller-00050-g5b7c893ed5ed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events_unbound kfree_rcu_monitor <snip> kfree_rcu_monitor() rearms the work if a "krcp" has to be still offloaded and this is done without holding krcp->lock, whereas the kvfree_call_rcu() holds it. Fix it by acquiring the "krcp->lock" for kfree_rcu_monitor() so both functions do not race anymore.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu KCSAN reports a data race when access the krcp->monitor_work.timer.expires variable in the schedule_delayed_monitor_work() function: <snip> BUG: KCSAN: data-race in __mod_timer / kvfree_call_rcu read to 0xffff888237d1cce8 of 8 bytes by task 10149 on cpu 1: schedule_delayed_monitor_work kernel/rcu/tree.c:3520 [inline] kvfree_call_rcu+0x3b8/0x510 kernel/rcu/tree.c:3839 trie_update_elem+0x47c/0x620 kernel/bpf/lpm_trie.c:441 bpf_map_update_value+0x324/0x350 kernel/bpf/syscall.c:203 generic_map_update_batch+0x401/0x520 kernel/bpf/syscall.c:1849 bpf_map_do_batch+0x28c/0x3f0 kernel/bpf/syscall.c:5143 __sys_bpf+0x2e5/0x7a0 __do_sys_bpf kernel/bpf/syscall.c:5741 [inline] __se_sys_bpf kernel/bpf/syscall.c:5739 [inline] __x64_sys_bpf+0x43/0x50 kernel/bpf/syscall.c:5739 x64_sys_call+0x2625/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f write to 0xffff888237d1cce8 of 8 bytes by task 56 on cpu 0: __mod_timer+0x578/0x7f0 kernel/time/timer.c:1173 add_timer_global+0x51/0x70 kernel/time/timer.c:1330 __queue_delayed_work+0x127/0x1a0 kernel/workqueue.c:2523 queue_delayed_work_on+0xdf/0x190 kernel/workqueue.c:2552 queue_delayed_work include/linux/workqueue.h:677 [inline] schedule_delayed_monitor_work kernel/rcu/tree.c:3525 [inline] kfree_rcu_monitor+0x5e8/0x660 kernel/rcu/tree.c:3643 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391 kthread+0x1d1/0x210 kernel/kthread.c:389 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Reported by Kernel Concurrency Sanitizer on: CPU: 0 UID: 0 PID: 56 Comm: kworker/u8:4 Not tainted 6.12.0-rc2-syzkaller-00050-g5b7c893ed5ed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: events_unbound kfree_rcu_monitor <snip> kfree_rcu_monitor() rearms the work if a "krcp" has to be still offloaded and this is done without holding krcp->lock, whereas the kvfree_call_rcu() holds it. Fix it by acquiring the "krcp->lock" for kfree_rcu_monitor() so both functions do not race anymore.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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
High: exploitation depends on specific conditions
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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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-362
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-3756Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen, Daten zu manipulieren oder nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241225Security Bulletin 25 Dec 2024

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

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-53110 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=CVE-2024-53113 Référence CVE CVE-2024-53117 https://www.cve.org/CVERecord?id=CVE-2024-53117 Référence CVE CVE-2024-53118 https://www.cve.org/CVERecord?id=CVE-2024-53118 Référence CVE CVE-2024-53120 https://www.cve.org/CVERecord?id=CVE-2024-53120 Référence CVE CVE-2024-53123 https://www.cve.org/CVERecord?id=CVE-2024-53123 Référence CVE CVE-2024-53134 https://www.cve.org/CVERecord?id=CVE-2024-53134 Référence CVE CVE-2024-53136 https://www.cve.org/CVERecord?id=CVE-2024-53136 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53167 https://www.cve.org/CVERecord?id=CVE-2024-53167 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53185 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-53147 Référence CVE CVE-2024-53148 https://www.cve.org/CVERecord?id=CVE-2024-53148 Référence CVE CVE-2024-53150 https://www.cve.org/CVERecord?id=CVE-2024-53150 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53154 https://www.cve.org/CVERecord?id=CVE-2024-53154 Référence CVE CVE-2024-53155 https://www.cve.org/CVERecord?id=CVE-2024-53155 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53163 https://www.cve.org/CVERecord?id=CVE-2024-53163 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-53165 https://www.cve.org/CVERecord?id=CVE-2024-53165 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53169 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-53147 Référence CVE CVE-2024-53148 https://www.cve.org/CVERecord?id=CVE-2024-53148 Référence CVE CVE-2024-53150 https://www.cve.org/CVERecord?id=CVE-2024-53150 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53154 https://www.cve.org/CVERecord?id=CVE-2024-53154 Référence CVE CVE-2024-53155 https://www.cve.org/CVERecord?id=CVE-2024-53155 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53163 https://www.cve.org/CVERecord?id=CVE-2024-53163 Référence CVE CVE-2024-53165 https://www.cve.org/CVERecord?id=CVE-2024-53165 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53150 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53152 https://www.cve.org/CVERecord?id=CVE-2024-53152 Référence CVE CVE-2024-53153 https://www.cve.org/CVERecord?id=CVE-2024-53153 Référence CVE CVE-2024-53154 https://www.cve.org/CVERecord?id=CVE-2024-53154 Référence CVE CVE-2024-53155 https://www.cve.org/CVERecord?id=CVE-2024-53155 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53163 https://www.cve.org/CVERecord?id=CVE-2024-53163 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-53165 https://www.cve.org/CVERecord?id=CVE-2024-53165 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53167 https://www.cve.org/CVERecord?id=CVE-2024-53167 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53150 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53152 https://www.cve.org/CVERecord?id=CVE-2024-53152 Référence CVE CVE-2024-53153 https://www.cve.org/CVERecord?id=CVE-2024-53153 Référence CVE CVE-2024-53154 https://www.cve.org/CVERecord?id=CVE-2024-53154 Référence CVE CVE-2024-53155 https://www.cve.org/CVERecord?id=CVE-2024-53155 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53163 https://www.cve.org/CVERecord?id=CVE-2024-53163 Référence CVE CVE-2024-53165 https://www.cve.org/CVERecord?id=CVE-2024-53165 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53167 https://www.cve.org/CVERecord?id=CVE-2024-53167 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53169 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-53148 Référence CVE CVE-2024-53150 https://www.cve.org/CVERecord?id=CVE-2024-53150 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53154 https://www.cve.org/CVERecord?id=CVE-2024-53154 Référence CVE CVE-2024-53155 https://www.cve.org/CVERecord?id=CVE-2024-53155 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53159 https://www.cve.org/CVERecord?id=CVE-2024-53159 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53171 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53148 Référence CVE CVE-2024-53150 https://www.cve.org/CVERecord?id=CVE-2024-53150 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53154 https://www.cve.org/CVERecord?id=CVE-2024-53154 Référence CVE CVE-2024-53155 https://www.cve.org/CVERecord?id=CVE-2024-53155 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53159 https://www.cve.org/CVERecord?id=CVE-2024-53159 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53171 https://www.cve.org/CVERecord?id=CVE-2024-53171 Référence CVE CVE-2024-53173 https://www.cve.org/CVERecord?id=CVE-2024-53173 Référence CVE CVE-2024-53174 https://www.cve.org/CVERecord?id=CVE-2024-53174 Référence CVE CVE-2024-53179 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53148 Référence CVE CVE-2024-53150 https://www.cve.org/CVERecord?id=CVE-2024-53150 Référence CVE CVE-2024-53151 https://www.cve.org/CVERecord?id=CVE-2024-53151 Référence CVE CVE-2024-53154 https://www.cve.org/CVERecord?id=CVE-2024-53154 Référence CVE CVE-2024-53155 https://www.cve.org/CVERecord?id=CVE-2024-53155 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-53157 https://www.cve.org/CVERecord?id=CVE-2024-53157 Référence CVE CVE-2024-53158 https://www.cve.org/CVERecord?id=CVE-2024-53158 Référence CVE CVE-2024-53159 https://www.cve.org/CVERecord?id=CVE-2024-53159 Référence CVE CVE-2024-53160 https://www.cve.org/CVERecord?id=CVE-2024-53160 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-53162 https://www.cve.org/CVERecord?id=CVE-2024-53162 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-53169 https://www.cve.org/CVERecord?id=CVE-2024-53169 Référence CVE CVE-2024-53171 https://www.cve.org/CVERecord?id=CVE-2024-53171 Référence CVE CVE-2024-53173 https://www.cve.org/CVERecord?id=CVE-2024-53173 Référence CVE CVE-2024-53174 https://www.cve.org/CVERecord?id=CVE-2024-53174 Référence CVE CVE-2024-53179 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028127Linux の 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: < 6.3, 6.6.64 ≤ 6.6.*, 6.11.11 ≤ 6.11.*, 6.12.2 ≤ 6.12.*, 6.13 ≤ *
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 24 Dec 2024 · Last source change 11 May 2026, 20:51 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-51832
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-51832↗Vendor CSAF · SUSE Product Security Team↗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-53160 · cve.blacktree.nl