CVE Intelligence
Medium Memory corruption

CVE-2024-41023 — sched/deadline: Fix task_struct reference leak

In the Linux kernel, the following vulnerability has been resolved: sched/deadline: Fix task_struct reference leak During the execution of the following stress test with linux-rt: stress-ng --cyclic 30 --timeout 30 --minimize --quiet kmemleak frequently reported a memory leak concerning the task_struct: unreferenced object 0xffff8881305b8000 (size 16136): comm "stress-ng", pid 614, jiffies 4294883961 (age 286.412s) object hex dump (first 32 bytes): 02 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .@.............. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ debug hex dump (first 16 bytes): 53 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 S............... backtrace: [<00000000046b6790>] dup_task_struct+0x30/0x540 [<00000000c5ca0f0b>] copy_process+0x3d9/0x50e0 [<00000000ced59777>] kernel_clone+0xb0/0x770 [<00000000a50befdc>] __do_sys_clone+0xb6/0xf0 [<000000001dbf2008>] do_syscall_64+0x5d/0xf0 [<00000000552900ff>] entry_SYSCALL_64_after_hwframe+0x6e/0x76 The issue occurs in start_dl_timer(), which increments the task_struct reference count and sets a timer. The timer callback, dl_task_timer, is supposed to decrement the reference count upon expiration. However, if enqueue_task_dl() is called before the timer expires and cancels it, the reference count is not decremented, leading to the leak. This patch fixes the reference leak by ensuring the task_struct reference count is properly decremented when the timer is canceled.

Published Jul 29, 2024 · Updated Oct 21, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.29%
ahead of 21% of scored CVEs · Oct 20, 2026
Affects
Linux
Linux and 1 more
CVSS base
5.5
Medium · 1 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 5.10≥ 5.4.212 and < 5.5≥ 4.19.257 and < 4.20version 184c8ab5342450c4ae6fc5d937f9bb06c620dcf1version f0e1c1d8ff908a39dd42e723d08f104505dfa601≥ feff2e65efd8d84cf831668e182b2ce73c604bbb and < b58652db66c910c2245f5bee7deca41c12d707b9≥ feff2e65efd8d84cf831668e182b2ce73c604bbb and < 7a54d31face626f62de415ebe77b43f76c3ffaf4≥ feff2e65efd8d84cf831668e182b2ce73c604bbb and < f8005214946fd1d9fefdeff19c6ce46d60de2cef Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel version 6.10-rc7≥ 4.19.257 and < 4.20version 6.10-rc6version 6.10-rc5version 6.10-rc4version 6.10-rc3version 6.10-rc2version 6.10-rc1
and 2 more ≥ 5.10 and < 6.9.10≥ 5.4.212 and < 5.5
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.1 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-401 · Missing Release of Memory after Effective Lifetime

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 21, 2026
  • Fix documented
    Oct 21, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux kernel
    Oct 21, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • 2024
  • CVE published
    Jul 29, 2024 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 21, 2026 – Oct 21, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

5 on the record

Elsewhere on this site

Linux
every CVE for this vendor
Memory corruption
same class
CWE-401
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-98869 bpf: Infer zext_dst based on static register liveness analysis 8h
  • CVE-2023-7356 Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID 8h
  • CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 3d
  • CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 3d
  • CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 3d
  • CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 3d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2024-41023 is "sched/deadline: Fix task_struct reference leak", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.29% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.