Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set element timeout

Noroxi assessment

Priority: Monitor (action score 28/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.26% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 0d40e8cb1d1f56a994cdd2e015af622fdca9ed4d, 383182db8d58c4237772ba0764cded4938a235c3, 7395dfacfff65e9938ac0889dafa1ab01e987d15; Azure Linux 3.0 ARM 6.6.56.1-1; Azure Linux 3.0 x64 6.6.56.1-1.

Low priority for now. Upgrade to Linux Linux 0d40e8cb1d1f56a994cdd2e015af622fdca9ed4d, 383182db8d58c4237772ba0764cded4938a235c3, 7395dfacfff65e9938ac0889dafa1ab01e987d15; Azure Linux 3.0 ARM 6.6.56.1-1; Azure Linux 3.0 x64 6.6.56.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: netfilter: nf_tables: use timestamp to check for set element timeout Add a timestamp field at the beginning of the transaction, store it in the nftables per-netns area. Update set backend .insert, .deactivate and sync gc path to use the timestamp, this avoids that an element expires while control plane transaction is still unfinished. .lookup and .update, which are used from packet path, still use the current time to check if the element has expired. And .get path and dump also since this runs lockless under rcu read size lock. Then, there is async gc which also needs to check the current time since it runs asynchronously from a workqueue.

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
May 14, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 17th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 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.

CNA vs NVD score

NVD
7.0
CNA · Linux
7.8
0.8 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-27397

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.

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 kernel4.1 and later · before 4.19.320
  • linux linux kernel4.20 and later · before 5.4.282
  • linux linux kernel5.5 and later · before 5.10.224
  • linux linux kernel5.11 and later · before 5.15.165
  • linux linux kernel5.16 and later · before 6.1.97
  • linux linux kernel6.2 and later · before 6.6.84
  • linux linux kernel6.7 and later · before 6.7.5
  • linux linux kernel6.8

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

    • 4.1affected
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before f8dfda798650241c1692058713ca4fef8e429061affected · git
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before eaf1a29ea5d7dba8e84e9e9f3b3f47d0cd540bfeaffected · git
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before 7b17de2a71e56c10335b565cc7ad238e6d984379affected · git
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before 0d40e8cb1d1f56a994cdd2e015af622fdca9ed4daffected · git
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before b45176b869673417ace338b87cf9cdb66e2eeb01affected · git
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before 7fa2e2960fff8322ce2ded57b5f8e9cbc450b967affected · git
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before 383182db8d58c4237772ba0764cded4938a235c3affected · git
    • c3e1b005ed1cc068fc9d454a6e745830d55d251d and later · before 7395dfacfff65e9938ac0889dafa1ab01e987d15affected · git
    • before 4.1not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.26.1.el9_47.3.0-427.26.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4

+96

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-27395May 14, 2024 · net: openvswitch: Fix Use-After-Free in ovs_ct_exit
    31Monitor
  • ← EarlierCVE-2024-27396May 14, 2024 · net: gtp: Fix Use-After-Free in gtp_dellink
    31Monitor
  • Later →CVE-2023-52657May 17, 2024 · Revert "drm/amd/pm: resolve reboot exception for si oland"
    22Monitor

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 Linux0d40e8cb1d1f56a994cdd2e015af622fdca9ed4dVendor (CNA)
Linux Linux383182db8d58c4237772ba0764cded4938a235c3Vendor (CNA)
Linux Linux7395dfacfff65e9938ac0889dafa1ab01e987d15Vendor (CNA)
Linux Linux7b17de2a71e56c10335b565cc7ad238e6d984379Vendor (CNA)
Linux Linux7fa2e2960fff8322ce2ded57b5f8e9cbc450b967Vendor (CNA)
Linux Linuxb45176b869673417ace338b87cf9cdb66e2eeb01Vendor (CNA)
Linux Linuxeaf1a29ea5d7dba8e84e9e9f3b3f47d0cd540bfeVendor (CNA)
Linux Linuxf8dfda798650241c1692058713ca4fef8e429061Vendor (CNA)
Azure Linux 3.0 ARM6.6.56.1-1 · hyperv-daemonsMicrosoft (MSRC)
Azure Linux 3.0 x646.6.56.1-1 · hyperv-daemonsMicrosoft (MSRC)
CBL Mariner 2.0 ARM5.15.167.1-1 · hyperv-daemonsMicrosoft (MSRC)
CBL Mariner 2.0 x645.15.167.1-1 · hyperv-daemonsMicrosoft (MSRC)
almalinux:bpftool7.3.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.99-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.119-1~deb11u1 · Debian:11Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)

+33

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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

All records