dbcve.org
Linux KernelOperating system · Linux

CVE-2024-35898

HIGH · 7.0 CVSS v3.1 Published 2024-05-19
Fix available
A fix is available. Upgrade to 4.19.312 / 5.4.274 or later.
See remediation →
72/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: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() nft_unregister_flowtable_type() within nf_flow_inet_module_exit() can concurrent with __nft_flowtable_type_get() within nf_tables_newflowtable(). And thhere is not any protection when iterate over nf_tables_flowtables list in __nft_flowtable_type_get(). Therefore, there is pertential data-race of nf_tables_flowtables list entry. Use list_for_each_entry_rcu() to iterate over nf_tables_flowtables list in __nft_flowtable_type_get(), and use rcu_read_lock() in the caller nft_flowtable_type_get() to protect the entire type query process.

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:>= 4.16, < 4.19.312>= 4.20, < 5.4.274>= 5.5, < 5.10.215>= 5.11, < 5.15.154>= 5.16, < 6.1.85>= 6.2, < 6.6.26>= 6.7, < 6.8.5= 6.9
Debian LinuxOperating system
Affected:= 10.0

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 4.19.312 / 5.4.274 / 5.10.215 or later
Fixed in 4.19.3125.4.2745.10.215
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel >= 4.19.312 (for 4.19.x branch), >= 5.4.274 (for 5.4.x branch), >= 5.10.215 (for 5.10.x branch), >= 5.15.154 (for 5.15.x branch), or a later stable release

  1. 1. Identify the currently running kernel version using `uname -r`
  2. 2. Check if your distribution provides a newer kernel version that includes the fix (kernel version >= 4.19.312, >= 5.4.274, >= 5.10.215, or >= 5.15.154 depending on your base kernel branch)
  3. 3. For Debian 10 (Buster), consider upgrading to Debian 11 (Bullseye) or Debian 12 (Bookworm) which include patched kernels, or apply the upstream kernel patch from commit 24225011d81b471acc0e1e315b7d9905459a6304
  4. 4. Update the kernel package using your distribution's package manager (e.g., `apt-get update && apt-get install linux-image-<version>` on Debian/Ubuntu)
  5. 5. Reboot the system to load the patched kernel
  6. 6. Verify the fix is applied by checking the kernel version and confirming the patch is included (`grep -i flowtable /boot/config-$(uname -r)`)
Caveat Kernel upgrades may require rebooting and could introduce compatibility issues with custom kernel modules or older system utilities; ensure backup 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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35898 — 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-35898 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