Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-57977: memcg: fix soft lockup in the OOM process

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 0a09d56e1682c951046bf15542b3e9553046c9f6, 110399858194c71f11afefad6e7be9e3876b284f, 46576834291869457d4772bb7df72d7c2bb3d57f; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.82.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.82.1-1.

Low priority for now. Upgrade to Linux Linux 0a09d56e1682c951046bf15542b3e9553046c9f6, 110399858194c71f11afefad6e7be9e3876b284f, 46576834291869457d4772bb7df72d7c2bb3d57f; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.82.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.82.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: memcg: fix soft lockup in the OOM process A soft lockup issue was found in the product with about 56,000 tasks were in the OOM cgroup, it was traversing them when the soft lockup was triggered. watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [VM Thread:1503066] CPU: 2 PID: 1503066 Comm: VM Thread Kdump: loaded Tainted: G Hardware name: Huawei Cloud OpenStack Nova, BIOS RIP: 0010:console_unlock+0x343/0x540 RSP: 0000:ffffb751447db9a0 EFLAGS: 00000247 ORIG_RAX: ffffffffffffff13 RAX: 0000000000000001 RBX: 0000000000000000 RCX: 00000000ffffffff RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000247 RBP: ffffffffafc71f90 R08: 0000000000000000 R09: 0000000000000040 R10: 0000000000000080 R11: 0000000000000000 R12: ffffffffafc74bd0 R13: ffffffffaf60a220 R14: 0000000000000247 R15: 0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2fe6ad91f0 CR3: 00000004b2076003 CR4: 0000000000360ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: vprintk_emit+0x193/0x280 printk+0x52/0x6e dump_task+0x114/0x130 mem_cgroup_scan_tasks+0x76/0x100 dump_header+0x1fe/0x210 oom_kill_process+0xd1/0x100 out_of_memory+0x125/0x570 mem_cgroup_out_of_memory+0xb5/0xd0 try_charge+0x720/0x770 mem_cgroup_try_charge+0x86/0x180 mem_cgroup_try_charge_delay+0x1c/0x40 do_anonymous_page+0xb5/0x390 handle_mm_fault+0xc4/0x1f0 This is because thousands of processes are in the OOM cgroup, it takes a long time to traverse all of them. As a result, this lead to soft lockup in the OOM process. To fix this issue, call 'cond_resched' in the 'mem_cgroup_scan_tasks' function per 1000 iterations. For global OOM, call 'touch_softlockup_watchdog' per 1000 iterations to avoid this issue.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 27, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2024-57977

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

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

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.6 and later · before 6.12.13
  • linux linux kernel6.13 and later · before 6.13.2

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

    • 3.6affected
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before 72f2c0b7c152c2983ed51d48c3272cab4f34d965affected · git
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before 110399858194c71f11afefad6e7be9e3876b284faffected · git
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before a9042dbc1ed4bf25a5f5c699d10c3d676abf8ca2affected · git
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before 0a09d56e1682c951046bf15542b3e9553046c9f6affected · git
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before 972486d37169fe85035e81b8c5dff21f70df1173affected · git
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before c3a3741db8c1202aa959c77df3a4c361612d1eb1affected · git
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before 46576834291869457d4772bb7df72d7c2bb3d57faffected · git
    • 9cbb78bb314360a860a8b23723971cb6fcb54176 and later · before ade81479c7dda1ce3eedb215c78bc615bbd04f06affected · git
    • before 3.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64kbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debugbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-develbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-cross-headersbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debugbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-develbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-57975Feb 27, 2025 · btrfs: do proper folio cleanup when run_delalloc_nocow() failed
    22Monitor
  • ← EarlierCVE-2024-57976Feb 27, 2025 · btrfs: do proper folio cleanup when cow_file_range() failed
    22Monitor
  • Later →CVE-2024-57979Feb 27, 2025 · pps: Fix a use-after-free
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0a09d56e1682c951046bf15542b3e9553046c9f6Vendor (CNA)
Linux Linux110399858194c71f11afefad6e7be9e3876b284fVendor (CNA)
Linux Linux46576834291869457d4772bb7df72d7c2bb3d57fVendor (CNA)
Linux Linux72f2c0b7c152c2983ed51d48c3272cab4f34d965Vendor (CNA)
Linux Linux972486d37169fe85035e81b8c5dff21f70df1173Vendor (CNA)
Linux Linuxa9042dbc1ed4bf25a5f5c699d10c3d676abf8ca2Vendor (CNA)
Linux Linuxade81479c7dda1ce3eedb215c78bc615bbd04f06Vendor (CNA)
Linux Linuxc3a3741db8c1202aa959c77df3a4c361612d1eb1Vendor (CNA)
azl3 kernel 6.6.82.1-1 on Azure Linux 3.06.6.82.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.82.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.05.15.179.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.05.15.179.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)

+9

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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-667 · Improper Locking

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

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (14 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records