dbcve.org
Linux KernelOperating system · Linux

CVE-2024-53122

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-02
Fix available
A fix is available. Upgrade to 6.1.119 / 6.6.63 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust Additional active subflows - i.e. created by the in kernel path manager - are included into the subflow list before starting the 3whs. A racing recvmsg() spooling data received on an already established subflow would unconditionally call tcp_cleanup_rbuf() on all the current subflows, potentially hitting a divide by zero error on the newly created ones. Explicitly check that the subflow is in a suitable state before invoking tcp_cleanup_rbuf().

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-362

Two operations that should be atomic can interleave, so an attacker who wins a narrow timing window reaches an inconsistent, exploitable state. These bugs are subtle and easy to miss in review. Fixing them properly means correct locking or atomic operations around the shared resource.

General guidance for the race condition class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.10, < 6.1.119>= 6.2, < 6.6.63>= 6.7, < 6.11.10= 6.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.119 / 6.6.63 / 6.11.10 or later
Fixed in 6.1.1196.6.636.11.10
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 6.1.119+ (for 5.10-6.1.x), 6.6.63+ (for 6.2-6.6.x), 6.11.10+ (for 6.7-6.11.x), or 6.12.1+ (for 6.12.x)

  1. 1. Identify the current running kernel version using `uname -r`
  2. 2. Determine the appropriate fixed kernel version based on your current version: for 5.10-6.1.x upgrade to 6.1.119 or later; for 6.2-6.6.x upgrade to 6.6.63 or later; for 6.7-6.11.x upgrade to 6.11.10 or later; for 6.12.x upgrade to 6.12.1 or later
  3. 3. Update the package repository and install the new kernel version using your distribution's package manager (e.g., `apt update && apt install linux-image-<version>` for Debian/Ubuntu, or `yum update kernel` for RHEL/CentOS)
  4. 4. Reboot the system to load the new kernel: `systemctl reboot`
  5. 5. Verify the system is running the patched kernel using `uname -r` and confirm the version is at or above the fixed version for your branch
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with custom modules or older drivers; ensure backup of critical data and test in staging if possible

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-53122 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data