CVE-2024-56613: sched/numa: fix memory leak due to the overwritten vma->numab_state
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 5f1b64e9a9b7ee9cfd32c6b2fab796e29bfed075, 8f149bcc4d91ac92b32ff4949b291e6ed883dc42, a71ddd5b87cda687efa28e049e85e923689bcef9; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.
Low priority for now. Upgrade to Linux Linux 5f1b64e9a9b7ee9cfd32c6b2fab796e29bfed075, 8f149bcc4d91ac92b32ff4949b291e6ed883dc42, a71ddd5b87cda687efa28e049e85e923689bcef9; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: sched/numa: fix memory leak due to the overwritten vma->numab_state [Problem Description] When running the hackbench program of LTP, the following memory leak is reported by kmemleak. # /opt/ltp/testcases/bin/hackbench 20 thread 1000 Running with 20*40 (== 800) tasks. # dmesg | grep kmemleak ... kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak) # cat /sys/kernel/debug/kmemleak unreferenced object 0xffff888cd8ca2c40 (size 64): comm "hackbench", pid 17142, jiffies 4299780315 hex dump (first 32 bytes): ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00 .tI.....L.I..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc bff18fd4): [<ffffffff81419a89>] __kmalloc_cache_noprof+0x2f9/0x3f0 [<ffffffff8113f715>] task_numa_work+0x725/0xa00 [<ffffffff8110f878>] task_work_run+0x58/0x90 [<ffffffff81ddd9f8>] syscall_exit_to_user_mode+0x1c8/0x1e0 [<ffffffff81dd78d5>] do_syscall_64+0x85/0x150 [<ffffffff81e0012b>] entry_SYSCALL_64_after_hwframe+0x76/0x7e ... This issue can be consistently reproduced on three different servers: * a 448-core server * a 256-core server * a 192-core server [Root Cause] Since multiple threads are created by the hackbench program (along with the command argument 'thread'), a shared vma might be accessed by two or more cores simultaneously. When two or more cores observe that vma->numab_state is NULL at the same time, vma->numab_state will be overwritten. Although current code ensures that only one thread scans the VMAs in a single 'numa_scan_period', there might be a chance for another thread to enter in the next 'numa_scan_period' while we have not gotten till numab_state allocation [1]. Note that the command `/opt/ltp/testcases/bin/hackbench 50 process 1000` cannot the reproduce the issue. It is verified with 200+ test runs. [Solution] Use the cmpxchg atomic operation to ensure that only one thread executes the vma->numab_state assignment. [1] https://lore.kernel.org/lkml/1794be3c-358c-4cdc-a43d-a1f841d91ef7@amd.com/
- Published
- Dec 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-401
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.4affected
- ef6a22b70f6d90449a5c797b8968a682824e2011 and later · before 8f149bcc4d91ac92b32ff4949b291e6ed883dc42affected · git
- ef6a22b70f6d90449a5c797b8968a682824e2011 and later · before a71ddd5b87cda687efa28e049e85e923689bcef9affected · git
- ef6a22b70f6d90449a5c797b8968a682824e2011 and later · before 5f1b64e9a9b7ee9cfd32c6b2fab796e29bfed075affected · git
- before 6.4not affected · semver
- 6.6.66 and later · up to and including 6.6.*not affected · semver
- 6.12.5 and later · up to and including 6.12.*not affected · semver
- 6.13 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.4 and later · before 6.6.66
- linux linux kernel6.7 and later · before 6.12.5
- linux linux kernel6.13
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.5-1 | 6.12.5-1 |
| openSUSE:Leap 15.6 | dtb-aarch64 | before 6.4.0-150600.23.60.3 | 6.4.0-150600.23.60.3 |
| openSUSE:Leap 15.6 | kernel-64kb | before 6.4.0-150600.23.60.4 | 6.4.0-150600.23.60.4 |
| openSUSE:Leap 15.6 | kernel-azure | before 6.4.0-150600.8.43.1 | 6.4.0-150600.8.43.1 |
| openSUSE:Leap 15.6 | kernel-debug | before 6.4.0-150600.23.60.4 | 6.4.0-150600.23.60.4 |
| openSUSE:Leap 15.6 | kernel-default | before 6.4.0-150600.23.60.5 | 6.4.0-150600.23.60.5 |
| openSUSE:Leap 15.6 | kernel-default-base | before 6.4.0-150600.23.60.5.150600.12.26.4 | 6.4.0-150600.23.60.5.150600.12.26.4 |
| openSUSE:Leap 15.6 | kernel-docs | before 6.4.0-150600.23.60.3 | 6.4.0-150600.23.60.3 |
| openSUSE:Leap 15.6 | kernel-kvmsmall | before 6.4.0-150600.23.60.4 | 6.4.0-150600.23.60.4 |
| openSUSE:Leap 15.6 | kernel-obs-build | before 6.4.0-150600.23.60.3 | 6.4.0-150600.23.60.3 |
| openSUSE:Leap 15.6 | kernel-obs-qa | before 6.4.0-150600.23.60.2 | 6.4.0-150600.23.60.2 |
| openSUSE:Leap 15.6 | kernel-rt | before 6.4.0-150600.10.44.1 | 6.4.0-150600.10.44.1 |
| openSUSE:Leap 15.6 | kernel-rt_debug | before 6.4.0-150600.10.44.1 | 6.4.0-150600.10.44.1 |
| openSUSE:Leap 15.6 | kernel-source | before 6.4.0-150600.23.60.4 | 6.4.0-150600.23.60.4 |
| openSUSE:Leap 15.6 | kernel-source-azure | before 6.4.0-150600.8.43.1 | 6.4.0-150600.8.43.1 |
| openSUSE:Leap 15.6 | kernel-source-rt | before 6.4.0-150600.10.44.1 | 6.4.0-150600.10.44.1 |
| openSUSE:Leap 15.6 | kernel-syms | before 6.4.0-150600.23.60.4 | 6.4.0-150600.23.60.4 |
| openSUSE:Leap 15.6 | kernel-syms-azure | before 6.4.0-150600.8.43.1 | 6.4.0-150600.8.43.1 |
| openSUSE:Leap 15.6 | kernel-syms-rt | before 6.4.0-150600.10.44.1 | 6.4.0-150600.10.44.1 |
| openSUSE:Leap 15.6 | kernel-zfcpdump | before 6.4.0-150600.23.60.4 | 6.4.0-150600.23.60.4 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_13 | before 1-150600.13.6.4 | 1-150600.13.6.4 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_13 | before 1-150600.1.5.1 | 1-150600.1.5.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_2 | before 1-150700.15.3.1 | 1-150700.15.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_2 | before 1-150700.1.5.1 | 1-150700.1.5.1 |
+39
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-56610Dec 27, 2024 · kcsan: Turn report_filterlist_lock into a raw_spinlock22Monitor
- ← EarlierCVE-2024-56612Dec 27, 2024 · mm/gup: handle NULL pages in unpin_user_pages()22Monitor
- Later →CVE-2024-56614Dec 27, 2024 · xsk: fix OOB map writes when deleting elements31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5f1b64e9a9b7ee9cfd32c6b2fab796e29bfed075 | Vendor (CNA) |
| Linux Linux | 8f149bcc4d91ac92b32ff4949b291e6ed883dc42 | Vendor (CNA) |
| Linux Linux | a71ddd5b87cda687efa28e049e85e923689bcef9 | Vendor (CNA) |
| azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.5-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.4.0-150600.23.60.3 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.4.0-150600.23.60.4 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-azure | 6.4.0-150600.8.43.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-debug | 6.4.0-150600.23.60.4 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default | 6.4.0-150600.23.60.5 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.4.0-150600.23.60.5.150600.12.26.4 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-rt | 6.4.0-150600.10.44.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 6.4.0-150600.10.44.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-azure | 6.4.0-150600.8.43.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-rt | 6.4.0-150600.10.44.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 6.4.0-150600.8.43.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 6.4.0-150600.10.44.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-azure | 6.4.0-150600.8.43.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150700.53.6.1.150700.17.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-docs | 6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_13 | 1-150600.1.5.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_2 | 1-150700.15.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-obs-build | 6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150600.10.44.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-rt_debug | 6.4.0-150600.10.44.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-source-azure | 6.4.0-150600.8.43.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
+5
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.